Power Platform Community Forum Thread Details

Hello everyone!

I've been wondering what the best approach to this problem would be, as everything I've tried so far has been either unsuccessful or not particularly scalable.

I have multiple Dataverse tables that I am writing to from Power Apps (Table A, B, C), all with different data. I'd like to issue these all at once, in a single request that either succeeds or fails at once, or works sequentially but rolls back any changes upon failure. I've tried two solutions so far, the first being a Changeset request using the Dataverse connector in PA, but this doesn't seem to work as the amount of rows I am writing to in Tables B & C are dynamic, and the Dataverse connector doesn't allow apply to each. The other solution is in PowerApps, which is simply writing to the tables and encasing everything in nested IfErrors that rollback changes on failure. This is somewhat better, but I am worried about issues happening on those rollbacks themselves and creating even more issues. I've seen some options that look viable using the Web API (Execute batch operations using the Web API (Microsoft Dataverse) - Power Apps | Microsoft Learn/Dataverse Batch Requests in Power Automate - NETWORG Blog (thenetw.org)), but this is currently far outside my skillset.

Does anyone know of an easier way to do this? Or are my options simply between the good-but-higher-code solution and the worse-but-lower-code Power Apps solution?

Thanks!

Categories:

Microsoft Dataverse with Power Apps

Hi @JJWorkAcc,

Indeed, the Changeset action in PA is very limited, and most of the time I cannot use it as well, for instance, it doesn't support for each loops 😞 IfErrors would sort of work but very messy and error prone in my opinion. It doesn't actually rollup the transaction, you're just manually performing another update operation to "rollback", and these updates can fail and can end up in a corrupted state. The best way as you alluded to is more in a pro-code scenario with Web API or also with the SDK (.NET): https://learn.microsoft.com/dotnet/api/microsoft.xrm.sdk.messages.executetransactionrequest?view=dataverse-sdk-latest
Probably not the answer you were looking for but at least it is possible. Another option is to manage via a business process meaning, if an error occurs in the app, ensure you bubble up the error correctly to the users, update rows to an "error" state and have a easy way for the users to fix/address the error to bring back the system/records to a valid state.
Hope this helps!