8.5.2. Catalog update for ERP integration 8.5.2.3. Further information on the catalog update
|  |
| Prev | Next |
During a catalog update, the old and new versions are compared. This process runs according to the following scheme:
A comparison is made by project path [Project path], project name [Project name] and standard number [Standard number] to see whether the version has remained the same.
Points 1 and 2 are always implemented, even if there is no ERP integration.
The following point is only relevant if there is an ERP integration. See Section 4.15.3, “ Catalog update with ERP link - Fix assignment problems with Update Manager ” in PARTsolutions Administration - Manual .
Comparison of the project rows with field changes in the "ACTIVE_STATE" and "REQUESTED_STATE" columns
The following cases may occur when checking the project lines:
Lines without a link in the LinkDB
Additional project lines cannot have a cannot. There is no further check.
Lines with a link in the LinkDB
For all project lines that have a link in the LinkDB, a precise check of the changes (project, table, geometry) can be carried out.
In addition, before the update is carried out, the entries to be made in the "ACTIVE_STATE" and "REQUESTED_STATE" columns in the LinkDB are determined.
The following flowchart illustrates the processes involved in a catalog update:
