Skip to content
DemanderDemanderDemander Docs
Light
English

Skipping file in upload process

The synchronizer may return the message below:

Return from Webservice: Demander skipped importing this file. Reason: we received the same file in YYYY-MM-DD HH:MM:SS (Import ID: INTEGRATION-ID - ‘FILE NAME’).

A control was implemented in the process that receives data from the ERP that checks the content of the file and if it has already been sent in the last 12 hours, it is ignored and it is not imported.

We understand that the file has already been imported previously and there is no point in importing it again.

There are two scenarios involved:

  1. ERP only sends data that has changed since the last synchronization: In this case, in theory, there should be no rejection of files, because if at each synchronization only what changed from the previous to the current one is sent, there is no way for the same data to change in the next synchronization, only the same record can have a change in a field to a new value.
  2. ERP sends all data with each synchronization. In this case, it will be very normal for files to be rejected, because the same data will be sent repeatedly to Demander. For example: what is the chance that the city table will have any changes? In theory, all cities (normally from IBGE) will be in the file.

How is this evaluation done to determine that it is the same content in the file:

  • The file is received, and an MD5 HASH of its contents is generated.
  • We check whether this HASH has already been imported previously within a 12-hour interval.
  • If it has already been imported previously, the file in question is not imported.
  • If it has not been imported previously, the file in question is imported normally.