Question

I have a model, called Organisation and the model is stored in an assembly called Model. There is a requirement to insert an organisation and update an organisation.

Couple of questions:

When inserting a new organisation, I want to ensure that the organisation doesn’t already exist so I’ve inserted some remote validation. I then bind the model to the insert view.

Now, when I’m creating the update view should I use a different view model which removes the remote validation for duplicate organisation names? If so, I can’t use my base Organisation model for the update view, so do I then need to create 2 different views, one for insert and one for update? If this is the case, there is going to be 2 views that are basically the same but just use different models.

Can anyone help?

Answer 1

For this specific scenario the validation that no other organization with the same name exists seems valid for both the insert and update case so you could reuse the same view model.

However validating that the name does not exists when updating a organization must have extra because if the user does not change the organization name then at least one record on the database has that name, the one being updated, and the validation should ignore that record.

So if you choose to reuse the view model the validation must perform according to the context of the operation (insert or update).