In scenarios where data is exported, changed, and then reimported, the unique identifiers will be more reliable. Users are not expected to know the internal identifiers of a field, but they are exportable. The internal number is the more reliable identifier since it will never change, however, the name is more common and easier to find. Any destination field that has an ID/Name pair of input fields works the same way. When importing from a flat file, the Origin Template can be specified by mapping the internal numeric identifier to the Origin Template ID field, or by mapping the name to the Origin Template Name field. For example, each Origin Template has a name, but internally SixBit also keeps track of it by a number. You may notice in the SixBit 2.0 import many fields can be entered through either an ID or a Name. SixBit keeps track of some fields by use of an internal numeric identifier in addition to a human readable name. Most important to note is that the only time all fields can be updated from a single import is when an item is first being created.

One of the first changes you will likely notice is that the Import from File now has several options (Items, Suppliers/Consignors, Inventory, Compatibility Sets) and the Import From CSV window now has multiple tabs. All fields could be updated with a single import. In versions prior to SixBit 2.0, all fields that could be imported to, were located on one tab in the import window. You may find that your import files don’t work as before because of these changes. However, to allow for the robust improvements, changes to the import process were necessary. The upgrades to CSV import allow for the import of all types of data including Item/Supplier/Shipment/Sales/Buyer/Compatibility Sets/ Orders, including orders from other venuesthrough CSV. With the release of SixBit 2.0 the overall importing and exporting process has been upgraded to provide users with more control and options.

Turbo lister 2 csv template