Conflicts

The conflict occurs if the repository does not contain the database specified in SQL command connection. To resolve the conflict, click the hyperlink in the Conflict box and select a database:

It is available in the desktop application.

To resolve the conflict, click the hyperlink in the Conflict box: The Resolving Conflict dialog box opens:

The boxes are filled by default:

• Repository Version. The current version of updated repository object.

• Update Version. The current version of update file object.

After the Allow Update button is clicked, the object contents and the current version will be replaced with the update version.

It is available in the desktop application.

To resolve the conflict, click the hyperlink in the Conflict box. The Resolving Conflict dialog box opens:

The boxes are filled by default:

• Repository Version. The current version of updated repository object.

• Update Version. The current version of update file object.

After the Allow Update button is clicked, the object contents and the current version will be replaced with the update version.

The update object and the corresponding repository object belong to different types of objects on the basis of their keys or identifiers (for example, a table and a unit). It is prompted to create a new object to resolve the conflict.

This conflict cannot be resolved. It is recommended to open the file in the update manager and check the object update options. It is possible that the Update Objects Only update method is selected for the object, and no corresponding object is found in the repository.

Key or identifier matching depends on the selected update type. To resolve the conflict, click the hyperlink in the Conflict box:

It is prompted to create a new repository object with another name and identifier to resolve the conflict. The boxes are filled by default:

• The object name is taken from the update.

• Identifier is generated taking into account identifier format determined in the security manager.

This conflict cannot be resolved. It is recommended to open the file in the update manager and check the object update options. It is possible that object recreation is set in the update options, and the update file does not contain metadata required for this operation.

To resolve the conflict, click the hyperlink in the Conflict box. The Resolving Conflict dialog box opens:

The table contains missing and selected objects. Replace the missing objects with the repository objects by clicking the Select hyperlink.

To reset the selected object, click the Clear hyperlink.

After all the missing objects have been replaced, and the Allow Update button has been clicked, the object to update will contain the selected objects.

NOTE. If the update contains custom class objects and the conflict was caused by absence of custom classes with corresponding identifiers in the repository, this conflict can be resolved only in the desktop application.
If the update contains custom class objects and the conflict was caused by absence of custom classes in the repository, this conflict cannot be resolved in the update manager. To resolve the conflict, create required custom classes in the repository and install the update again.