1

For a current MVC3 project I have a model that has multiple pages for input. The object is set up with required fields however they're on different pages. This means I can't do a simple check on ModelState.IsValid. Instead I check if the current page has all the values it needs before allowing the user on to the next. This doesn't seem ideal.

One of the main things that I don't like is the fact that having required fields on a page other than the first means the postback and overall validation failure has already happened so any required fields on the next page are already marked in error state even though the user has never been to the page.

Are there any best practices for validation of an entity with multiple input pages that have required fields on them?

tereško
  • 58,060
  • 25
  • 98
  • 150
Casey Margell
  • 224
  • 2
  • 12

2 Answers2

3

You should use view models instead of your domain models. Soy you could split your domain model into multiple view models for each step of the wizard. Here's another answer you might find useful.

Community
  • 1
  • 1
Darin Dimitrov
  • 1,023,142
  • 271
  • 3,287
  • 2,928
  • +1. I think that view models are one of the lesser understood constructs in not just MVC, but DDD-related paradigms, in general. A lot of people try to force their entities to play both roles, and it often becomes a larger headache than a non-entity approach. – Joseph Ferris Feb 03 '11 at 19:14
  • You rock, thanks for the response and I'll check out view models. Does indeed appear to be the answer I'm looking for. – Casey Margell Feb 03 '11 at 19:18
  • Ok, followon question. I have a create post action. Does this mean I need a Create action for each ViewModel then? – Casey Margell Feb 03 '11 at 21:48
0

This is one reason why using a separate ViewModel for every page is recommended as a best practice, and using your Entity classes directly in the ViewModel is discouraged.

With separate ViewModels, you can tailor the attribute-based validation as needed. It will complicate things in that you will then need to find a way to map between the ViewModels and your Entities.

quentin-starin
  • 26,121
  • 7
  • 68
  • 86