CSV Load Discrepancies
Issue: Full bundles with modified images content are ignored during the CSV transformation.
The CSV bundle Transform process has an in-built checksum logic to filter out that content which is not updated after the last load. This process works only on the CSV content and it does not consider the external objects such as IMAGEs, PDFs, XMLs, and so on.
When you want to update any of these external objects, the default transform process ignores the updates as the same data is already loaded. To update these external objects, you must set the Ignore Checksum flag to true during the data load process. Typically, this loads the entire bundle again as if all the contents are new.
To avoid this, you must update the value of one of columns in the CSV row (entry) in which the external object is referenced. For some objects like a part or a parts list, you can update any of the existing attributes.
Let us consider a use case where you have some data in Parts.csv as:
|
Part Code
|
Name
|
Image
|
|---|---|---|
|
PA001
|
PART 001
|
Image1.jpg
|
Subsequently you realize that Image1.jpg is not correct and needs to be updated. You update the image and publish the bundle (Parts.csv) again as:
|
Part Code
|
Name
|
Image
|
|---|---|---|
|
PA001
|
PART 001
|
Image1.jpg
|
However, when you try to load the bundle, the PA001 specific entry is ignored as the application finds similar data already loaded.
To load this data, you must adopt one of following two strategies:
• Load data with the Ignore Checksum flag set to true.
• Update the data and load the new bundle Parts.csv (update any existing fields such as the Name as shown in the following table).
|
Part Code
|
Name
|
Image
|
|---|---|---|
|
PA001
|
PART 001 Updated
|
Image1.jpg
|
 |
The Ignore Checksum flag must be used only for specific instances like missed external objects or data load failure. Otherwise usage of this flag is restricted.
|