Note

Up to and including V9, a customer administrator had to perform a mapping for LinkDB datasets with every catalog update using the Update Manager [Update manager] if projects or variables had been changed. In order to relieve the customer side, as of V10, mapping information is integrated directly into the catalog. That means these tasks are now done by the modeller of the catalog before it is published. Only in exceptional cases the mapping has to be performed on customer side. See Section 6.10.2, “ Check ERP mapping (Add ERP mapping... and Edit ERP mapping...) ” in eCATALOGsolutions - Manual. For catalogs that are not yet prepared for automatic mapping, the Update Manager [Update manager] is still used in the event of assignment problems in the LinkDB.

What is the Update Manager used for?

With an ERP link, data records in the LinkDB are assigned to a specific project line (project path + LineID).

During catalog updates, it can happen that not all LinkDB links are found for every product due to changes.

Reasons for catalog changes may be:

Update manager

In the Update Manager [Update manager], you have an overview of all projects, project lines, variables and variable values. In the Information -> Geometric similar [Geometrical similarity] ity section, you can see if the component has changed geometrically.

On the left you can select individual projects and lines in the directory structure. On the right you can see the current mapping. With a click on the respective icon you can confirm or revoke assignments.

The command Confirm assignment [Approve assignment] command immediately changes the values in the Active State and Requested State columns. You can find details on this at Section 4.15.3.5.1, “ACTIVE_STATE and REQUESTED_STATE ”.

Two examples will be used to illustrate how to work with the Update Manager [Update manager].