Data Access has been discontinued. Please refer to this page for more information.

The persistent class uses the BackendCalculated generator and a composite primary key but its Identity Mechanism Member is not synchronized with its columns

This article is relevant to entity models that utilize the deprecated Visual Studio integration of Telerik Data Access. The current documentation of the Data Access framework is available here.

This error occurs when a persistent class in the domain model uses the BackendCalculated generator but its selected Identity Mechanism Member is not synchronized with any of the Backend Calculated columns of the respective table.

Solution

To resolve this error you can either select different key generator for the persistent type, or select which one of the primary key members will use Autoinc key generator.

To select different key generator:

  • Double-click the error to open the Validation Dialog.
  • Select the Select key generator for the persistent tipe option.
  • From the drop-down list choose the key generator you wish to use.

  • Click the Fix Selected button.

To select which one of the pimary key members will use Autoinc key generator:

  • Double-click the error to open the Validation Dialog.
  • Select the Select one of the primary key members which will use the Autoinc key generator option.
  • From the drop-down list choose the member which should use the Autoinc key generator.

  • Click the Fix Selected button.

Further References