tmpcl wrote:
I'm using 3.0 Final.
I have a View in which I designated a "primary key" in the designer so that I could establish a relationship between it and an Entity. The relationship works great until I attempt to refresh the model to bring in any changes from the database. Once I do that I receive the results below and the manual relationship is removed.
The relationship 'db.View - db.Entity (1:1)' has been removed because its underlying foreign key constraint wasn't found in the refreshed relational model data.
How can I specify to always maintain this manually configured relationship even though it of course does not exist in the database?
I just ran into the same issue. In "Preferences" under the "Catalog Refresher" category set "RelationshipsFollowDBForeignKeyConstraints" to false.
The will preserve any relationship that were manually created in the designer. The only bad thing about this is you now have to manually add any new relationship that was created in your database. I think there needs to be a 3rd option (still sync the automatic relationships but keep the manual ones).