For everyone who may have this problem and who does not want to recreate their EDMX:
I had a similar problem, which was repeated several times, which I was able to fix by filtering the list of errors using "Assembly Only".
As soon as I did this, I discovered a number of errors regarding multiplicity conflicts that I could solve by going to the Model Browser in the Association and changing the values of End1 and End2 Multiplicity (if applicable).
In my case, deleting the ability of the FK column to be null (in the database) led to the fact that the constructor of entities could not preserve the multiplicity 1..1. Switching to 0..1 fixed the problem.
source share