I am using LLBLGen with the MS SQL Server against a database that I cannot control. The database has many lookup tables that have a Guid PK AND and column that is defined as following
integer
Identity
Unique constraint
LLBLGen 5.2 doens't recognize these FKs and doesn't provide a navigation property to the parent table. Also, I'm unable to add model-only FKs (which is a great feature!), as the table already has a PK that is duly offerd!
Is it possible to have LLBLGen generate the needed navigation properties?
In the Designer, you can un-check "Is PK" for the GUID PK, and mark it for the UC field.
Then you can define a custom (model-only) relation between the 2 entities.
You're likely using database first development, so also make sure you're UNchecking the setting Entity Model -> Database First Development -> Identifying fields follow dbprimary key constraints, otherwise a refresh will reset the changed pk fields.