Nullable foreign keys seen but not used

This may be by design, but I've noticed that if I have Radzen generate CRUD pages on a table that relates to child tables via nullable foreign keys ("Enforce foreign key constraint" set to "no" in SQL Server), the child tables are listed in the "Include:" dropdown, but the resulting page does not use the foreign keys to setup dropdowns, etc.

Its easy enough to manually fix the page later, but this does take quiet a bit of extra time.


Another note, if you do find an issue with this, could you also look at operability with the dropdowndatagrid? I switched a perfectly functional dropdown to a dropdowndatagrid using the same nullable FK, and it wouldn't build.

Hi @SloSuenos,

Could you send us the SQL CREATE script of that database to

Done. Let me know if you have any questions.