Setting Up Selected Object Update Options

To view and set up update options of the selected object, use the Object Update Options panel. By default, the panel is located under the Update panel with the list of update objects.

When the Update Objects root item is selected on the Object Update Options panel, the common options of all the update objects are displayed:

The Update List option is applied to the repository objects, special repository objects and their access permissions.

NOTE. The Update List parameter is absent in the web application. The Object Only option is selected for the update list by default.

Select the elements to update in the drop-down list:

Object Only. Only the object is transferred. Default.
Access Permissions Only. The access permissions to the repository and special objects are transferred.
Object with Access Permissions. The access permissions to the repository objects and special objects and objects themselves are transferred.

NOTE. If on transferring access permissions it is required to update them at DBMS level, select the Grant Access Permissions at the DBMS Level checkbox in the update options.

Setting the root element value affects all the update objects. If the Update List option is different for the objects in the update, the value of this element is not displayed for the Update Objects root item.

Select the update type in the drop-down list:

By Keys. Objects are updated by keys. Default.
By Identifiers. Objects are updated by identifiers. The option is applied to the objects included into update.

On selecting the update type take into account the following:

Correspondence of the dependent objects not included into the update file is always tracked on the consumer schema by keys, even if the update file is saved with the By Identifiers option. Therefore, before saving the update file it is recommended to include all dependent objects to update. To do this, select the Consists Of context menu item of the object update tree and select all objects in the dialog box that opens.
If the By Identifiers update type is set, and form components have the changed objects, to which they referred, on updating components they are updated and reconfigured to the other object.

Select the update method in the drop-down list:

Always Create New Objects.
Create New Objects and Update Existing. Default.
Update Objects Only.

Determine whether dependent objects are cleared on update.

Dependent objects should be cleaned when the objects that refer to each other are updated.

NOTE. If the option is enabled, it is not available to update separately object data and object metadata for linked objects.

The Object Update option is displayed only for the objects, which enable object's data and metadata to be updated separately (all table types and MDM dictionaries, automatic cubes).

Select object update type:

Object Data. Only object data is updated.
Object Data and Metadata. The structure and data of the object are updated.
Object Metadata. Only the structure of the object is updated.

The update option coincides with the update method specified in the Add Object to Update dialog box. This option affects the Update Method and the Recreate on Update options.

The option is relevant for:

Tables, MDM dictionaries and automatic cubes if the Data or Data and Metadata items are selected for the Object Update option.
Time series databases.

Determine the object data update method.

Default. Object data is overwritten.
Overwrite All Data. All data of the object is overwritten. An updated object is cleaned before the update.
Append Only. New entries are added to object data. Existing entries are not refreshed.
Change Only. Object data is updated but no new entries are added.
Update and Change. Object data is updated, new entries are added to the data. Entries and elements missing in the source object are saved to the updated object.

On setting up this option pay attention to the value set for the primary key.

Determine update type. Options are the same as those specified for a root element. An additional option is also available:

Default. Object is updated by the method specified for the Update Objects root item. Default.

Determine the object update method. The same options as for a root element are available. The default method is Update Objects Only.

NOTE. The option is not available for all types of tables and for MDM dictionaries and automatic cubes where only data update is required.

Determine the update condition for an object, based on which the object can be excluded from the update during updating.

To determine condition:

Click the button.
Double-click the box with the main mouse button.

The Formula Editor dialog box opens. The formula editor shows current update flags that can be used to create a condition. On changing a condition for the object containing child elements it is requested whether to update all the nested elements.

NOTE. The confirmation message is displayed independently on whether there are update conditions for the nested objects.

Determine whether objects are skipped on update:

Yes. The object is kept in the update structure and is marked with the additional icon. On installing the update this object is not updated. When the Yes value is set for the folder, the confirmation message to change the properties values of the child objects is displayed.
No. Default. A negative answer does not change the properties values for child objects but sets the No value for the folder.

Object key is displayed in the box. Read-only.

The Data Filter option is relevant only for automatic cubes if the Data or the Data and Metadata item is selected for the Object Update option.

Set up displaying of selection by dimensions. To set the volume of moved data, click the button or double-click the box. The Data Filter dialog box opens:

Select filtering option:

Only Selected Data. Select the elements of dimensions, which data needs to be moved.
All Existing Data.

The Integrity Constraint option is relevant only for tables and MDM dictionaries. Determines behavior of an update if the updated object contains elements or entries that are not contained in the update and for which there are references from other dictionaries. Selection is executed in the drop-down list. The same options that are described for the Add Object to Update dialog box.

The option is available only for MDM dictionaries.

Determine whether access attributes are replaced on update:

Yes. Default. Values of attributes responsible for access permissions to MDM dictionary elements are updated.
No. Attribute values are not updated.

Remember that access attributes will be updated only if the user has a privilege to change permissions, otherwise the error message is displayed on update.

Set parameter values.

The option is relevant only for parametric automatic cubes.

Determines whether user credentials should be prompted if permissions of the current user are not sufficient to insert data to tables on update:

No. Default. If permissions to enter data are missing, user credentials are not prompted, an error occurs.
Yes. User credentials with permissions to create a table and insert the data in the corresponding database are prompted. The option is relevant only for inserting data to table.

Specify table fields, in which data is stored, in the Primary Key box. Based on these fields the system checks if data of the consumer table differs from data of the source table and executes the specified update operation (for example, only add records that are missing based on the primary key).

This parameter is available only for tables. If the table has a primary key, the filed automatically displays identifiers of those fields that are primary keys.

The fields data is separated by a semicolon.

The option is available for all types of tables, stored procedures and views if the Data or Data and Metadata items are selected for the Object Update parameter.

Determine when the object must be recreated at the DBMS level.

Default. Settings determined in the update settings will be used.
Always.
Do not Recreate. Default.

The parameter is available for security subjects.

Determine whether user group membership is saved on transferring security subjects between repositories:

No. Default. The group and its users are transferred between repositories without saving group membership.
Yes. The group and its users are transferred with saving group membership. To transfer group membership to update, it is required to add both the group and its users. All or single users can be transferred with saving group membership:

To transfer with saving group membership for all users, set the value either for the group, or for all its users.
To transfer single users with saving group membership, set the value only for those users.

After the update is installed, the users and the groups are transferred with saving group membership.

NOTE. When an update is created in the web application, only the Skip Object and Object Key parameters are available.