Product data imports
      Back to home
      1. Home
      2. Product Data Management
      3. Product data imports

      Importing an export file generated in SyncForce back into SyncForce, how does it work?

      Explanation on the functionality & checks applicable when importing a SyncForce export back into SyncForce.

      Limitations for security purposes

      The functionality to import Exports & Reports generated in SyncForce has the following limitations for security purposes:

      • On the Live environment it's only possible to import export files generated on the Live environment for this customer. Files generated on for example the Cloud environment cannot be imported on the Live environment.
      • On the other environments (Cloud / TST) it's possible to import export files generated on ALL environments for this customer. So there is no check on whether the file has been generated on the same environment.
      • Exports / Reports exported for customer A cannot be imported for customer B.
      • The export and the import need to match. So for example a 'PDM Master data template' export can only be imported in the Exports & Reports page where the 'PDM Master data template' export is generated.

      ImportKey & PersistenceKey

      The Exports & Reports which can be imported into SyncForce again contain 2 keys on the 'Instructions and Parameters' tab:

      • ImportKey; this key is generated specifically for this customer, this environment (Live, Cloud or TST) and this report file.
      • PersistenceKey; this key is a combination of the customer and the import route which will be used when importing this file.

      These keys are used to determine if the file can be imported.

      Scenarios

      Scenario Explanation Error message
      File does not contain an ImportKey This can be the case for export files generated before the Import functionality became available in SyncForce. The file does not contain an ImportKey or this ImportKey is not valid. (E0001)
      File contains an ImportKey but this is not known for this customer and/or environment File has been generated for another customer or it's generated on another environment than Live. This import file has not been generated for this customer on this environment and cannot be imported. (E0002)
      File contains an ImportKey but it's not valid The key has been altered (accidentally). The file does not contain an ImportKey or this ImportKey is not valid. (E0001)
      File does not contain a PersistenceKey This can be the case for export files generated before the Import functionality became available in SyncForce.

      When there is no PersistenceKey line in the Excel file (old export), the validation check is on ImportKey. This ImportKey needs to be available for this customer on this environment. When something is wrong with this ImportKey, the messages related to the ImportKey are shown.
      File contains a PersistenceKey but it does not match with the customer and/or import the user is uploading the file for File has been generated for another customer or the user tries to upload it on the wrong page (export & import not the same). This import file has not been generated for this customer and cannot be imported. (E0004)
      File contains a PersistenceKey but it's not valid The key has been altered (accidentally). This import file has not been generated for this customer and cannot be imported. (E0004)