Performing a changeset request in Microsoft Dataverse using Power Automate is a powerful way to ensure that multiple operations are executed atomically. This means that all operations succeed or none do, maintaining data consistency and integrity. In this blog, we’ll explore how to set up and execute a changeset request using Power Automate.

What is a Changeset in Dataverse?

A changeset in Dataverse is a group of operations that are treated as a single transaction. If any operation in the changeset fails, all the other operations are rolled back. This ensures data integrity and is especially useful for scenarios where multiple records need to be updated, created, or deleted simultaneously.

Prerequisites

1. Access to Power Automate.
2. A Dataverse environment.
3. Necessary permissions to perform operations in Dataverse.

Step-by-Step Guide to Perform a Changeset Request

Step 1: Create a Flow in Power Automate

1. Go to Power Automate.
2. Select Create > Automated cloud flow.
3. Provide a name for the flow and choose your desired trigger (e.g., When a record is created).

Step 2: Search and Add the Changeset Action

1. Select New Step.
2. In the Choose an operation card, search for `changeset`.
3. Select Perform a changeset request under Microsoft Dataverse.

4. A changeset scope will be added t o your flow.

Step 3: Add Actions to the Changeset Scope

Once the changeset container is added, follow these steps to include your desired operations:

1. Click on Add an action within the changeset scope.
2. Choose from the following available actions:
   • Add a new row: This action allows you to add a new row in the selected Microsoft Dataverse table.
   • Delete a row: This action allows you to delete a row from a Microsoft Dataverse table.
   • Update a row: This action allows you to modify any selected row in a Microsoft Dataverse table.
   • Upsert a row: This action allows you to modify any selected row in a Microsoft Dataverse table, or adds a new row if it doesn’t exist.
3. Configure the actions by specifying the necessary parameters like table name, row ID, or data values.

Step 4: Test and Validate

1. Save your flow.
2. Test it using sample data to ensure the changeset operations are correctly executed.
3. Verify that if any one of the actions fails, all the actions in the changeset are rolled back.

Real-World Use Cases for Changeset Requests

Changesets are particularly beneficial in scenarios such as:

• Order Management: Ensuring that order records, payment information, and shipment data are updated simultaneously.
• Employee Onboarding: Creating multiple records for a new hire, including personal information, payroll details, and IT system access, in one transaction.
• Inventory Management: Performing bulk updates to inventory data when stock is received or adjusted

Common Pitfalls and Troubleshooting Tips

Here are some common issues and tips to resolve them:

• Unsupported Actions: Ensure only supported actions (Add a new row, Delete a row, Update a row, or Upsert a row) are used within the changeset scope.
• Output Referencing Errors: You cannot reference outputs of previous actions within the changeset. Plan accordingly.
• Testing Issues: If changes are not reflecting, verify permissions and ensure there are no data validation errors.
• Rollback Issues: Check the flow run history for detailed error logs to identify which action caused the rollback.

Limitations of Changeset Requests

While changesets are useful, they come with certain limitations:

• Limited Actions: Only Add a new row, Delete a row, Update a row, and Upsert a row are supported.
• No Conditional Operations: Actions like Apply to each or conditions within the changeset are not supported.
• No Output Referencing: You cannot use the output of a previous action within a changeset.
• Designer Limitations: Changeset requests are currently not supported in the AI-powered cloud flows designer.

Conclusion

Using a changeset request in Dataverse ensures your data remains consistent by performing multiple operations atomically. This feature is particularly beneficial for complex business scenarios where multiple related records must be updated together.

Now that you have a clear understanding of how to perform a changeset request using Power Automate, try implementing it in your environment and streamline your data management processes.

Feel fre to comment down below if you face any issues. I’ll be happy to help.

Happy Automating!

Related Links

• Perform a changeset request using Power Automate
• Microsoft Dataverse Overview
• Create and Manage Cloud Flows
• Microsoft Dataverse Connectors