During this stage, the GUIDs are loaded back into Smart Reference Data.
When a part class (or custom interface) is transferred to a Smart 3D catalog, and that part class did not exist there before, Smart 3D requires a unique identifier for it. Hence, the software looks in the GUIDs data table that comes with the transfer run to determine if a GUID string is provided there for the new part class. If this is not the case, the software automatically creates a new GUID for the part class and also adds this GUID to the GUIDs data table in the transferred workbook.
During this stage, all GUIDs that have been newly created in Smart 3D can be added to the template that was attached to the current transfer run. The user is prompted to upload the workbook that contains the GUIDs data table with the Smart 3D values.
Identical rows are not added to the template data, but the import operation does not check for unique relations between the part classes and GUIDs during import.
Thus, it could happen that the same part class gets different GUIDs, for example, if the Smart 3D catalog was loaded with new part classes before, without also transmitting the actual GUIDs data table from Smart Reference Data.
The import operation does not touch existing records in the GUIDs template data; it only adds new rows if applicable.
After the new GUIDs have been imported into the Smart Reference Data template, they do not appear in the inventory until after the COMPLETE_JOB stage finishes in the current job run. In the next job run only, the new GUIDs are picked up from the template data, written into the job result, loaded into the Smart 3D catalog, and written into the destination inventory during the COMPLETE_JOB stage.
Smart Reference Data handles AMD indicators like in other data sets when transferring GUIDs to Smart 3D. For example, if the user deletes entries from the template data and posts the GUIDs to inventory, the removed rows will also disappear from the inventory.
Smart 3D ignores AMD indicators on the GUIDs data table.
The software also ignores duplicate entries and only considers the first one found. If a part class already exists in the Smart 3D catalog, and the GUIDs data table from Smart Reference Data contains the same part class with a different GUID string, the software does not generate errors during load, because the GUIDs data table data is not validated by Smart 3D. If a part class already exists in the Smart 3D catalog, but the GUIDs data table from Smart Reference Data does not contain an entry for this part class, no error occurs and Smart 3D does not create the entry on the data table. Furthermore, it is not possible to update GUIDs in the Smart 3D catalog. So, only apply changes in the GUIDs template data that are also supported on the Smart 3D side.
If config item AUTO_MAINTAIN_GUIDS is set to Y, the GUIDs data table is selected for the job automatically. This takes place only if the job contains either CustomInterfaces or PartClasses as its selected data tables.
Additionally, the job validation inserts new lines into the GUIDs template that result from the new custom interface and/or new part class definitions. (The software expects the interfaces to be defined on Integration > Smart 3D > Smart 3D Configuration > Attributes) New GUID numbers are generated where required.
When transmitting the data to Smart 3D using the Load API, the IMP_GUIDS stage becomes meaningless. However, the import of new GUIDs takes place directly after the load to Smart 3D during the BULKLOAD stage. In that case, the user is not prompted for workbook upload.