CODEWITHSUNDEEP
asp.net-mvcentity-frameworkpostgresqldevart
Etienne Desgagné
Etienne Desgagné

Reputation: 3252

Entity Framework complaining about required fields when saveChanges even if valid data are setted

I'm using Entity Framework (DbContext with database first) with MVC. When user save from a form, I have a condition in the controller that send the entity to the update of insert method depending of some internal flag of mine.

When sending entity to the update method, I flag it to modified using context.Entry(myEntity).State = EntityState.Modified;, I call saveChanges() and everything work well.

When sending the entity to the insert method, I flag it to added using context.Entry(myEntity).State = EntityState.Added; but when calling saveChanges() I receive error about 2 fields that are required...

The problem is that thoses 2 fields are not empty and they effectively contain valid data just before saving... I have even try to force new values to thoses 2 fields just before saving but same error.

It may be usefull to mention that I'm using Devart DotConnect For PostgreSQL as db provider.

Any idea how to debug this problem?

EDIT:

Here is the error:

Validation failed for one or more entities. See 'EntityValidationErrors' property for more details.

When looking for this EntityValidationErrors I receive the 2 following specific errors:

The flg_actif field is required

The user_creation field is required

As mentionned before, those fields are filled with data just before saving so I don't understand what is happening.

I'm using EF v4.0.30319 (system.data.entity=> v4.0 and EntityFramework=> v4.4)

EDIT2: Just to clarify a little bit more: The entity I'm trying to insert already exist in database. The form show the data of this database row. When saving, I decide if I update the row (this work well) but sometime, I need to insert the edited row as a new register instead of updating it to keep an history of the change in database.

Upvotes: 5

Views: 5832

Answers (1)

Nick
Nick

Reputation: 2325

Could you verify if the EntityKey property is set or null on the items you are trying to save?

If it already has a key, the context is already aware of the item, and you should use Attach instead of setting the state to added manually.

EDIT: To summarise the point from below. It looks like what you are doing is inserting a new copy of a row already associated with a context. That is almost certainly your problem. Try creating a fresh object based on your original row (i.e. copy the variable values or use a copy constructor), then add that new object.

Additionally, you should not need to set the state manually on a newly added object. You are trying to force the state here because the context doesn't see that item as a new one.

Upvotes: 2

Related Questions