Update Installation Features

Some repository objects have features of update installation.

Updating MDM Dictionaries

When transferring an MDM dictionary, new keys of dictionary child objects (tables and procedures) will be generated, which differ from those of the target repository.

Possible situations during updating of MDM dictionaries, which attributes refer to repository objects:

All dependent objects were added to the update. Update is correct.
Not all dependent objects were added to the update, and objects with the specified keys are not found in the consumer. It is checked if empty value is allowed for an MDM dictionary reference attribute:

For MDM dictionary attributes that allow for an empty value, empty value is written.
For MDM dictionary attributes that do not allow for an empty value, dictionary update is aborted, and an error is shown that the attribute does not allow for empty values.

Not all dependent objects were added to the update but in the target repository:

Correspondence is found by keys between repository objects. MDM dictionary is updated correctly by linking to existing objects.
Correspondence is not found by keys between objects and dependent objects that were not included in the update. A dialog box opens for replacing a missing object. If the user:

Agrees to replace an object. It is required to select an appropriate repository object. MDM dictionary is linked to the selected object.
Rejects to replace an object. The attributes that allow for an empty value are set to NULL. For the attributes that do not allow for an empty value, an error is displayed that attribute does not allow for empty values.

Updating Data Model

When a data model is added to the update, all objects included in this model are added to the update.

If the data model uses ClickHouse server connection:

Only object structures are transferred in the update file:

Tables and queries to the repository that uses connection to Foresight Analytics Platform.
Tables to the repository that uses the ClickHouse connection.

After installing the update:

For data model tables, which sources are flat files .xlsx and .csv, reload files.
For data model tables, which sources are non-flat files, the system starts materialization if the Automatic Refresh switch is in active state.

If the data model is used as a data source of information panels in the data retrieval mode, after transferring the information panel between the repositories refresh data model before its first saving.