Prevent Excel Drop Leading Zeroes in CSV Item Number Field
When I export Elliott's Item Number to CSV through either Export Processor, or Elliott provided reports with CSV export option, the leading zeroes will be dropped when I open it with Excel. For example, item number 0100, when open the CSV in Excel, it is displayed as 100. I found the following article that can address this issue:
This article suggest instead of exporting item number 0100 in the CSV as "0100", we can add a equal sign "=" in the front to make it ="0100", this way, Excel will preserve the leading zero.
This has been addressed for the following fields – item number, 25 character PO number, tracking number, and UPC codes. The change will be available in the next Elliott release. For further information on this change, refer to http://support.elliott.com/knowledgebase/articles/1832839-feature-prevent-excel-drop-leading-zeroes-in-csv concerning the changes for Elliott reports with CSV support and http://support.elliott.com/knowledgebase/articles/1833061-feature-equal-sign-support-in-export-processor concerning changes to the V8.2 Export Processor.
Daniel Knopp - Design Works Crafts Inc. commented
It's not just the Item_no field that is an issue. Our issue is with the item_note field that contains the upc information which always starts with a leading zero. I hope that if the global setup flag solution would address this field as well.
I think we should have a global setup flag for this to be backward compatible. The global setup flag should be placed at the proper record ID to reduce potential extra programming effort of reading the NS Control Record.
Daniel Weissbard - CyberMAC Software LLC commented
We just had a client with this same issue. As a workaround, we're creating a txt file and opening it with excel, telling excel to import with , delimited, and then going to the item_no field and saying it's a text field. That way the leading 0's come, but it's a bit more work for the user.