I have a setup where customized a From of a simple SharePoint Document library. The library is to store and publish the latest and greatest version of company procedures and process manuals. Old (outdated) Document is first Renamed and then Replaced with the current and valid one.
In the first round when fill in the custom form I get error message and throws out without writing changes to SharePoint. Re-entering the same data again no more error message I get and changes are processed in the Document library.
Rather strange. Wonder what this could be, has anyone come across similar?
I remember in Flows having to construct a Document Update within a Loop, checking for the Conflict Error. There was a lag in the time of update versus the time of releasing the lock on the document, so I'd delay, loop, and try again until the Conflict Error Number wasn't encountered. (A little scary, as a user can hypothetically lock a document and go on vacation.)
If you want to stick with doing inside of the PowerApp, then I suppose you could try to implement your Save based on a Timer control that fires every minute until the conflict error doesn't occur, and the Document gets saved. Else, save from within a Flow, where you can use a Do...Until Loop.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
2
Share
Report
All responses (
Answers (
