Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8826349
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T07:06:50+00:00 2026-06-14T07:06:50+00:00

I am updating a record over multiple forms/pages like a wizard. I need to

  • 0

I am updating a record over multiple forms/pages like a wizard. I need to save after each form to the database. However this is only a partial record. The EF POCO model has all data annotations for all the properties(Fields), so I suspect when I save this partial record I will get an error.

So I am unsure of the simplest solution to this.

Some options I have thought of:

a) Create a View Model for each form. Data Annotations on View model instead of EF Domain Model.

b) Save specific properties, rather than SaveAll, in controller for view thereby not triggering validation for non relevant properties.

c) Some other solution…??

Many thanks in Advance,

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T07:06:51+00:00Added an answer on June 14, 2026 at 7:06 am

    Option 1. Validation probably (especially in your case) belongs on the view model anyway. If it is technically valid (DB constraint wise) to have a partially populated record, then this is further evidence that the validation belongs on the view.

    Additionally, by abstracting the validation to your view, you’re allowing other consuming applications to have their own validation logic.

    Additional thoughts:

    I will say, though, just as a side note that it’s a little awkward saving your data partially like you’re doing, and unless you have a really good reason (which I originally assumed you did), you may consider holding onto that data elsewhere (session) and persisting it together at the end of the wizard.

    This will allow better, more appropriate DB constraints for better data integrity. For example, if a whole record shouldn’t allow a null name, then allowing nulls for the sake of breaking your commits up for the wizard may cause more long term headaches.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am updating multiple records and after I click submit button I get the
I am updating a record in a SQLite database when the user presses an
I want to iterate over records in the database and update them. However since
I'm having problems updating a record. My document structure is something like this: _id
Suppose I have a process that is updating a record and encounters a record
About best practices on designing stored procedures, should a stored procedure updating a record
Have a problem with updating an existing record of my DB. In my view
After updating to php 5.3 one of our systems has developed an interesting bug.
Below is my query which is updating a record in the User table ,
I have written a simple stored procedure for updating a record which isn't working

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.