You’re offline. This is a read only version of the page.
Announcements
I have had a scenario where Dataverse has not been able to update a record because it is locked. This is fair enough and can happen in any multi-client environment.
When this happens Dataverse reports a HTTP 400 Bad Request response with the following:
Cannot obtain lock on resource:'[redacted]', mode:Update - stored procedure sp_getapplock returned error code -3. The lock request was chosen as a deadlock victim. This can occur when there are multiple update requests on the same record. Please retry the request.
However the Dataverse connector doesn't retry the request for HTTP 400 errors.
So I have a situation where Dataverse even states "Please retry the request.", but the connector won't retry the request.
While I can obviously get around this by building in my own parallel flow steps to retry in this case, I wouldn't want to add complex logic to every Dataverse updateon the off-chance that there may be a record lock.
To me this seems like Dataverse and the Power Automate Dataverse connector do not play together nicely.
I have been battling with Microsoft support on this issue but don't seem to get anyway.
Is there a way to exscalate this from support to become a defect which Microsoft will fix?
Share
Report
All responses (
Answers (
522
