Timeline for Version Conflict issue with JavaScript Client Object Model code
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2014 at 13:30 | vote | accept | Brandon Michael Hunter | ||
| Sep 16, 2014 at 14:19 | comment | added | Derek Gusoff | I took a closer look at the way we did it on a previous project, and we actually re-queried the list item and fetched the owshiddenversion that way. I'd like to get the solution posted up here, but I need to decouple some client-specific logic and it may be awhile before I get to that. I think we did it that way for expediency but I'm sure there's a way to guess what the version may be. | |
| Sep 15, 2014 at 18:04 | comment | added | Brandon Michael Hunter | When I get the owshiddenversion value from the library and set it's value in code, after the executeQueryAsync I still get version conflict issue. Can you help me understand how you used the SPServices to get around this issue? | |
| Sep 15, 2014 at 17:49 | comment | added | Derek Gusoff | I'm not sure...I've never used RefreshLoad. And the documentation on it does not seem very helpful either. I had this situation once before but I was using asmx/SPServices and I used the approach above. | |
| Sep 15, 2014 at 16:09 | comment | added | Brandon Michael Hunter | See I was thinking if I call the refreshLoad() function that would do it? Am I wrong? | |
| Sep 15, 2014 at 13:58 | history | answered | Derek Gusoff | CC BY-SA 3.0 |