Product information is unexpectedly overwritten, what could be the cause of this?

This document describes the possible reasons why product information is overwritten by a nightly import processing. This concerns the (DA) Bodset import in combination with the Cocosoft File Import (product sources). This combination of imports only runs on the da /da environment (DA Cooperatie).

From the above, it can be deduced that there are 2 active import routines at night, a BOD set import and a File Import. The BOD set import processes product mutation files from the DA, the File Import processes the 'Luxury products' source from Cocosoft. Both imports are connected to company 2, the DA Headquarters. When these imports encounter the same product (based on barcode), there is a possibility that one import will overwrite information from the other import.

By logging into company 2 (Headquarters) and viewing the mutation history of a modified product, it is possible to see which import process is responsible for a certain mutation.

If the user who performed the mutation is 'BOD Set import', then the mutations are managed and executed from an external source. The cause of any unexpected mutations should be sought in that source.

If the mutations were performed by the user 'Import', then the cause of unexpected mutations can be found in the 'Luxury import'. This import reads files and then mutates the products in RetailVista.

The 'Luxury import' source is only allowed to make product mutations on products that are not actively managed by the 'BOD set import', except for barcodes and purchase information. If an active purchase rule is active for the supplier 'DA Retailgroep' for an product, the luxury import will not propagate mutations to this product.

If the purchase has expired, however, the changes will still be processed.