MetaForeignKeyAssociation: Target member is not an identity member...

[Scott]

When will this be supported? See attached screenshot of error...

[Zoran]

Hello Scott,

 We have added this to our TODO list for our future versions. Since it requires major development in some core parts of our product, we have scheduled it for Q2 2012 together with some other major refactorings for the runtime handling of associations. This however is not absolute and final time-frame for the delivery of this feature as depending on the development cycle by then it could be implemented sooner or later than expected. It is a time-frame that you can have as orientation about when the feature will be released.

All the best,
Zoran
the Telerik team

[Scott]

Thanks.

[Christopher]

What is the status of this? A typical schema in my database is a one to many with foreign keys in the many table.

e.g. Customers have many addresses hence the CustomerId is in the Address table.

Without this feature I can't use OpenAccess.

[Ivailo]

Hi Christopher,

Thank you for your interest in Telerik OpenAccess ORM.

In your scenario, if the CustomerId that is located in the Address table is pointing to a column in Customers table that is a primary key, you should not have any problems using Telerik OpenAccess ORM. 

The limitation that was discussed in this thread, and still remains in the product, is about a foreign key that is pointing to a unique constraint column that is not a primary key. For example a CustomerId that is linked with an Id column in the Customer table, but that Id column is not a primary key for the Customers table. In all other cases you will be able to create an association easily.

For more information about associations in OpenAccess ORM, you can check this documentation section.

I would also recommend you to download and use the OpenAccess SDK application, which includes a lot of useful sample projects using OpenAccess ORM - that is the fastest way to get an idea about how the product is used and what are the main benefits. Also you can see some of the introductory videos on Telerik TV.

Let us know if you have any other questions.

Regards,
Ivailo
the Telerik team

[Jason]

This exception is still being encountered in Q3 2014. Has this at all been or scheduled to be addressed since the last post in Q1 2013? This would be a big help when dealing with third party databases where you have no control over the schema.

[Kristian Nikolov]

Hi Jason,

Indeed, Telerik Data Access does not currently support scenarios where a relation is defined between a Foreign Key and a Unique column. Adding support for such scenarios would be a completely new feature of the product. Therefore we have an existing feature request about this functionality. We would like to invite you to vote for it at our Feedback Portal. Doing so will help us prioritize its eventual implementation.

I hope this helps. Should you have additional questions, feel free to post at our forums again.

Regards,
Kristian Nikolov
Telerik