Home/ Questions/Q 8486607
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T20:59:32+00:00

SQL Server 2008R2 Entity Framework 4.x (early version) I recently changed a view within

  • 0
  • SQL Server 2008R2
  • Entity Framework 4.x (early version)

I recently changed a view within a SQL Server 2088 R2 instance so that it now contains some LEFT OUTER JOINS instead of INNER JOINS which causes some fields to contains NULL now. That leaves with a exception that this fields are not allowed to be null cause they are entity keys.

Please note that all files are Entity Keys

Please note that all shown are required to be entity keys and that the image just showing a part of the whole view.

So am I doing anything totally wrong? Is there any fix around or do I have to life with it.

Here’s one of the errors

Error 213 Running transformation: Key Part: ‘WorkStepId’ for type
OrderSummary is not valid. All parts of the key must be non nullable.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Entity keys are not allowed to be NULL. Entity Framework has to be able to determine the uniqueness of an entity by a combination of one or more keys. I don’t know your exact data circumstance, but there may be a way to work around this requirement, but it’s not very clean.

    A possible workaround is including logic in your view T-SQL to coalesce NULL values to a known “dummy” value. For instance, with your data above, you can set the two NULL values to be -1 on reads. However:

    • You will have to use some sort of validation logic or stored procedure on save to prevent bad data being persisted to the database if you are doing writes.
    • You have to be sure that only one row with two NULL values for WorkStepId and StepStatusId per Id can be returned.
    • 0