If the invoice history isn’t showing up on the website,
first thing to look for is bad characters that throw the number of tab
delimited columns off.
To find that, you can use: Windows Powershell:
cat .\InvoiceHistoryHeader.txt | %{
$a=$_.Split("`t"); if($a.length -ne 35) {Write-Host "Wrong #of
Columns Detected in Order:
"$a[0]"-"$a[1]"-"$a[2]"="$a.length;} }
Or Linux:
awk -F'\t' '{if(NF>35) print "Invalid #of Columns on
line#:"NR, "Order:"$1, $2}' ./InvoiceHistoryHeader.txt
The linux one can be run in CentOS, or even the Ubuntu
command line that you can start inside Windows 10, so if you have the file
locally on your windows machine, or on the SSI server, either command should
show you where the error is. (This can be adapted to find any file that has the wrong
number of columns, which is normally the ‘garbage character’ issue with any
file, just name the file, and change the 35 to whatever number of columns the
file is supposed to have)
For ShipTo's, of course, do the ship to check for the files. Also for the shipto's, the Tax Jurisdictions must all exist, if you give a customer shipto a tax jurisdiction that doesn't exist in the system (and likewise a Tax Code that Doesn't Exist), then the shipto imports will fail on the web.