BUG: Commas on Shipping Invoice create bad format error when uploading to customer eStacks #439

New Issue

2026-06-29T08:38:12Z

rob commented

2026-06-29 08:38:12 +00:00

If the total is $1,000 or over, the shipping invoice inserts a comma for the number. This causes a read error on the csv upload for the shipping invoice to the recepient's eStack. We have to open and delete the comma, then re-upload.

Addtion related issues to the CSV format are;

Does not save properly when one opens/edits/fixes it. If one merely presses Save, which is normal and used to work fine, the CSV data gets tossed into the A column and it default saves as unicode without us specifying it. This was never a problem pre-3 months ago-ish. We have to specifically remember use the Save As function and save as CSV typ since the Save As also defaults to unicode text.

Lastly, anytime we make edits (which seem unavoidable in reality), the entire data set get thrown to the top row, thus removing the header row space to have data start on row 10. I am 100% sure this is related to the unicode text thingy. I prefer we just get the new Rania templates in asap and also a .dat file as Tim mentioned. We can deal like this until post-UPS integration.

If the total is $1,000 or over, the shipping invoice inserts a comma for the number. This causes a read error on the csv upload for the shipping invoice to the recepient's eStack. We have to open and delete the comma, then re-upload. Addtion related issues to the CSV format are; - Does not save properly when one opens/edits/fixes it. If one merely presses Save, which is normal and used to work fine, the CSV data gets tossed into the A column and it default saves as unicode without us specifying it. This was never a problem pre-3 months ago-ish. We have to specifically remember use the Save As function and save as CSV typ since the Save As also defaults to unicode text. Lastly, anytime we make edits (which seem unavoidable in reality), the entire data set get thrown to the top row, thus removing the header row space to have data start on row 10. I am 100% sure this is related to the unicode text thingy. I prefer we just get the new Rania templates in asap and also a .dat file as Tim mentioned. We can deal like this until post-UPS integration.

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#439