Comparing to the CE, the PE comes with a timestamp detection feature that detects, based on
the date found in the
updated_at column, if the entity has changed since the last import.
The timestamp detection can be activated when invoking the appropriate import command. To activate it,
add the parameter
--use-timestamp=true when invoking the import, e. g.
vendor/bin/import-pro import:products --cache-enabled=true --use-timestamp=true
Do not forget to add the
The timestamp detection functionality has no additional configuration options. Instead, it uses the
configuration of the change-set detection to query whether or not the
updated_at date has been
changed since the last import. If so, processing the main row, as well as the rows or the store
views, if available, will be skipped.
Assuming that in many cases, where the connected PIM or ERP system is NOT able to provide a CSV file that only contains the deltas comparing to the last import, the timetamp detection may have a significant impact on performance, as only rows that contains changed data will be processed.
When the timestamp has been changed, further processing the import will automatically use the change-set
functionality. To avoid this, consider using the additional paramater