Some Foreign Keys are completely ignored casing INSERTs to fail

This is a follow up to #49, although I’m not sure if the issues are technically related, other than having been discovered in the same scenario (trying to manage the ASP.NET Core Identity data model with EasyData).

EasyData seems to ignore some FK columns in some entities. The corresponding column/value is not shown in the data grid, the field is not rendered at all in the CRUD form, and any INSERT will fail because the FK ends up being NULL.

Two examples:

• IdentityRoleClaim: EasyData shows Id, ClaimType and ClaimValue. The property/column RoleId is completely ignored;
• IdentityUserClaim: Same, we have Id, ClaimType and ClaimValue, and UserId is ignored;

Trying to create a new record on either table will fail with (example for IdentityUserClaim):

Ooops, smth went wrong

Cannot insert the value NULL into column ‘UserId’, table ‘EasyDataDB.dbo.AspNetUserClaims’; column does not allow nulls. INSERT fails. The statement has been terminated.

Steps to reproduce

• Create a new project with “Individual accounts” (dotnet new webapp --auth Individual)
• Setup EasyData
• Browse for example /easydata/IdentityRoleClaim or /easydata/IdentityUserClaim

Expected result

• An empty grid (as there are no records yet), including the column RoleId (for Identity Role Claim) and UserId (for Identity User Claim)
• Trying to add a new record should render the field RoleId / UserId, accordingly

Actual result

• The columns RoleId or UserId are not shown in the query
• The fields RoleId or UserId are not rendered in the CRUD form

[chaghi]

Hi, thanks for taking the time to explain that, I appreciate it! I can confirm that having rebuilt the frontend as per your instructions, the issue appears to be fixed.

[antifree]

Fixed in version 1.3.2. PR #51