Catalog Management

Learn how to manage catalog.

Catalogs values in Aurea.CRM are uniquely identified by the catalog value in the catalog base language and the tenant number. This unique key is used to match up catalog entries when importing catalog values. The catalog base language is defined in the Language info area in the Rights module. Only one language may be defined as the catalog base language, and the catalog base language must be the same on all stations in a distributed setup. CRM.cockpit checks that the catalog base language numbers in the package and target database match when importing packages.

Catalogs can only be maintained on a catalog maintenance station, which is defined in the station records, see Station in the Rights Module topic of the CRM.core Administrator Guide. Changes to catalog values are tracked in the Catalog Maintenance table on the catalog maintenance station. Both old and new catalog values are stored in the table whenever a value is added, changed or deleted. When catalog maintenance records are imported on other stations, the entries in these records are used to update catalog values on the target station (updating old catalogs value to new ones). This catalog maintenance information should be included when exporting upgrade packages to allow catalogs on the target station to be updated, see Exporting Packages . For more details on catalog management in Aurea.CRM, see Automatic Catalog Maintenance in the Aurea.CRM win Administrator Guide.

If you intend to maintain the catalog values used in your package, configure the development station and target stations as catalog maintenance stations and always include the catalog maintenance records when exporting the package once a target station has been initialized, see Transporting Catalogs using Catalog Maintenance Records.

Catalogs themselves can also be added to packages, and catalogs in the package can be imported on the target station. In this case, catalogs are imported in a similar manner to other package items and catalog entries are matched up using the unique key (text in the catalog base language + tenant number).

Catalogs can be referenced by a wide range of formats (e.g. conditions) and records. When transferring formats using CRM.cockpit, it is therefore important to ensure that the catalog value referenced by package items is identical in the base language on the target system.

For more details on the catalog numbers used by variable catalogs in base packages, see Vertical Independent Configuration.