Catalogue Update

You use the program CatalogueUpdate.exe in the HiCAD EXE directory to update catalogues. This program is normally started automatically, e.g. when HiCAD is updated. It can also be started manually, if catalogues are to be exchanged between customers.

Source	Path of the new/changed catalogues. For automatic updates the source is preset.
Target	Path of the catalogues to be replaced. The field is filled in automatically. Manual entries in this field are not possible.
Settings	Here you specify the settings for the update by activating or deactivating the checkboxes. Please note that the activation of the Retain user settings option is possible, but generally not recommended. If you have activated this setting, some tables may not be displayed correctly. If required, check the log file.
Versions	Previous If the update is performed automatically, the corresponding HiCAD version will be detected via the Registry and will be displayed in this field. If the update is performed manually, you can enter the version, e.g. 1601. This field is a mandatory field. Current The current HiCAD version is detected via the Registry and is displayed in this field. Manual entries in this field are not possible.

Please note:

When performing updates of catalogues (these are supplied and also changed by the ISD Group), only files will be updated (on a string level). Assignments of the catalogue entries to HELiOS will not be affected.

Some catalogue attributes, e.g. table columns, can be changed by the user, others not. Modifiable attributes are contained in the columns Custom1 - Custom5.

Changed rows will be identified accordingly (with MOD for "modified"). If the user has applied a change to a row, e.g. entered an article number in Custom1 and Custom2, the corresponding row will not be updated when the next catalogue update is made. This means that all values, and the entered article number, will be retained in this row.
As a simultaneous Catalogue Update from different clients can cause damage to the catalogue, you should only perform one update at a time. If the user starts another update, an appropriate message will be issued and the catalogue will be left unchanged.