LLBLGen 2.6 Final. Dynamic Data add-on support.

In the zip file I downloaded, there is a text file (DbEditorASPNETSelfServicing_Readme.txt) which says:

Dynamic Data assumes that any relation has both sides present, so you can't use relations which are partly hidden, you've to have a field mapped, which is visible, on both sides of the relation.

Can you please elaborate on this?

In my database I am using surrogate keys(just a trigger based sequence) as the primary key and the natural primary key is used as unique constraints.

Krish wrote:

In the zip file I downloaded, there is a text file (DbEditorASPNETSelfServicing_Readme.txt) which says:

Dynamic Data assumes that any relation has both sides present, so you can't use relations which are partly hidden, you've to have a field mapped, which is visible, on both sides of the relation.

Can you please elaborate on this?

That means that, at relations sub-tab at LLBLGen Designer you can't partially hide the relation.

For example, in the DB a realtion Customer<-Order exists and Order->Customer as well. These two-way relation is mapped to your LLBLGen entity model. LLBLGen Designer allows you to hide one side of the relation. For example: you want to hide thi Customer<-Order relation but keep the other (Customer->Order), then you are partially hiding the relation. You can't do that when usin DynamicData add-on. You either hide the relation completely or don't hide it at all.