4.16.3.  Catalog update with ERP integration - Fix mapping problems with the Update manager
4.16.3.1. Catalog update (Tutorial) - Example 1
Prev  Next

4.16.3.1. Catalog update (Tutorial) - Example 1

4.16.3.1.1. Preparation
4.16.3.1.2. Status after update installation to Bikecompany V2 and before editing with Update Manager
4.16.3.1.3. Editing in Update manager

When using an ERP integration, in the LinkDB, datasets are assigned to a certain project row (project path + LineID).

At catalog updates it may happen that not all LinkDB connections for each project can be found due to changes.

[Note]Note

  • You can find the sample files for this tutorial in your installation under $CADENAS\training\update_manager.

  • For text and figures the role "ecat" of the demo database has been used. In order to receive the "classical" Red/Green depiction the respective settings have been made under Status colors for catalog index.[75]

  • Here in this tutorial the following setting has been used for the Export condition.[76] 

    (ERP_PDM_NUMBER.NE.'')

    So the status light is on green, if an ERP_PDM_NUMBER exists.


[75] See Section 4.7.3.3.2, “ Status colors for catalog index - plinkgroups.cfg -> Block [Role_name] -> Key "COLORCONDITIONTREE<number>" ” -> Example 3.

[76] See Section 4.7.3.1.7, “ Export condition - plinkgroups.cfg -> Block [Role_name] -> Key "EXPORTRESTRICTION" ”.

Prev Up Next
4.16.3.  Catalog update with ERP integration - Fix mapping problems with the Update manager  Home 4.16.3.1.1. Preparation