Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

From my understanding from this post (http://sharepoint.stackexchange.com/questions/23597/best-practice-to-handle-items-modification-in-sharepoint-2007), SharePoint uses optimistic concurreny e.g.

  • User A opens up edit form and starts editing
  • User B opens up ...
  • User A saves
  • User B clicks save but SP warns them that the data has changed since they started editing and will make the user B view User A's changes and re-enter.

Currently, I have a HTML form that will allow user to edit some list items, so I was wondering what I should do in SPServices to do the following:

  • getting that SP warning message for User B and
  • getting that User A's changes into the HTML form so that User B can view it?
share|improve this question
add comment

1 Answer 1

up vote 0 down vote accepted

Each time you update an item, one of the fields returned is the latest changed date/time. You can build your concurrency logic using that date/time, looking at it vs. the date/time prior to your update. It will require a few extra Web Service calls, but if it's important to maintain integrity, it works.

share|improve this answer
    
I think that multi workflows (which you describe as concurrency logic) will be pretty useful. –  Anderson Karu Jan 5 '12 at 8:48
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.