Last post Dec 14, 2010 02:27 PM by mbcoop
Dec 14, 2010 07:44 AM|mbcoop|LINK
I am moving a web application from EntityData to DomainData and am finding a number of annoying differences.
The biggest one now is the lack lack of proper rendering of foreign key fields.
Using just the default templates, I stepped through the ForeignKey fieldtemplate, and saw that the "Field" property was null. In the EntityData model, this is populated.
The net is that foreign keys are just that -- the key, NOT the DisplayName of that row in the database.
Seems like a major hole -- if that is in fact the case.
Dec 14, 2010 02:27 PM|mbcoop|LINK
OK -- the difference in a DomainData site is that the related tables are not "Include"'d, so I modified the "gets" to included related tables -- and all is well.