At first get an overview if there are changes in the update catalog at all and if yes, how many and of what kind.
Furthermore it is relevant, how far the LinkDB datasets can be automatically assigned (mapped) in a mapping process despite possible changes.
If the automatic mapping process could be successfully performed, the release can be performed after a simple check.
If the automatic mapping process was not successful, the affected projects must be assigned to LinkDB datasets by using search functionality.
The following information sources are available to determine the most effective approach.
Under PARTadmin -> Category Catalog update -> Offline -> Check -> Status tab page you will receive a list of all projects with information on changes.
Under PARTadmin -> Category Catalog update -> Offline -> Compare you can see a catalog comparison [Catalog comparison] with display of the directory structure and table. Changes to the directory structure and name changes are immediately visible in the comparison.
On this see Section 4.15.3.2.4, “ PARTadmin - Check | Compare | Install”.
During the update installation
For a catalog update [Catalog update] with ERP integration, the CIP Installation dialog box appears by default.
You will be asked whether you would like to test the catalogs to be installed for possible conflicts in the LinkDB before installation. These can then be resolved in the Update Manager [Update manager] by reassigning them.
If you want to carry out a check, click on .
If no problems are detected, the installation will run through without any further notes.
If problems are detected, the CIP Installation dialog box appears again with information on data records that could not be mapped.
After the update installation, you will find further helpful information in the PARTlinkManager using the values from the ACTIVE_STATE and REQUESTED_STATE columns.
On this see Section 4.15.3.2.5, “ PARTlinkManager ”.