So, this error is most likely coming from SharePoint, so either they made a change to SP Online that is casuing it, or there was a connector chnage that is causing it.
@JKarnesBloomin, are you still experiencing this ETAG mismatch error?
Would you be able to provide a session ID and a fiddler trace? I can jump on a call and help you with this if you send me a PM.
I am also seeing this same issue with a submitform .. Intermittant issue... mostly does not work anymore but will sometime work in dev studio
Data Source is a Task list in SharePoint...
Have tried replacing the connector with no luck
Just started heppening in the last week or so..
Session ID: 88a3da59-3cb7-487c-84ed-b0070a160b4a
error message states
"Conflicts exist with Changes on the server, Please Reload. Server Response ETAG Mismatch
I found a pattern easy to reproduce
I republished the app and an item will save fine on the first edit and save but you will get this the second time you edit and try to save.
This is very consistant an easy to reproduce.
Open item and edit and save - no problem. Open another list item and save - no problem. Go back to first item and try and save - you get the error. Go to the second item that you edited and try and edit and you get he same error
So here is the pattern
Open an item and save - works fine. Open the saved item and edit and try and save - you get the error.
So Ill throw my app in the ring as well. Every app we use that connects to sharepoint is suffering from the dreaded ETAG issue. Just want to ditto what @skylitedave has described. I found the same pattern... I thought it was intermittant but when I refresh the browser and reload our apps the first save for each record will be sucessful. Any second edit throws an error, always the same error, and we have to refresh the browser and reload the app to clear it.
Microsoft must have changed something in the sourcecode with powerapps or sharepoint over the last week.
It is not a random error. It is easy to reproduce.
Happens every time
data source SharePoint lists
Workaround for now
This has been validated by several users
This has been open for a week with no updates from Microsoft.
Can someone from Microsoft respond and let us know what is going on to resolve this serious bug? This is being reported by many users.
To recap.. the issue is this....
If you connect to a SharePoint list and try to edit a list item more than 1 time in a session you will get this error when you use patch or submitform unless you issue a refresh ( and that is a suboptimal workaround since it involves a roundtrip to the server before you save)
Join us next Wednesday for our Demo Extravaganza, October 16, 2019 8am PDT.
Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.
Continue your learning in our online communities.
Features releasing from October 2019 through March 2020
Coming to a city near you
Fill out a quick form to claim your user group badge now!
Connect, share, and learn with your peers year-round
Register by September 5 to save $200