How to Trigger Power Automate Flows on Data Changes in Dynamics 365
Question details
The user needs to trigger a Power Automate flow specifically when data changes (data events) in a Dynamics 365 Finance and Operations table, rather than relying solely on business events.

- Product
- Microsoft Power Automate and Dynamics 365 Finance and Operations
- Device & OS
- not provided
- Scenario
- Automating business workflows based on specific record modifications or value updates within a D365 F&O table.
- Observed behavior
- The standard Dynamics 365 F&O connector natively displays business events, making it unclear how to configure the system for direct data events or specific field value change triggers.
Ensure you have administrative access to your Power Automate environment and Dynamics 365 Finance and Operations instance to configure connectors and check event catalogs.
Use the Dataverse Connector for Data Events via Virtual Tables
Since direct D365 F&O data events might not natively appear in the legacy connector, routing via Dataverse virtual entities is the recommended modern approach for triggering flows on data changes.
Microsoft integrates Dynamics 365 Finance and Operations tightly with Dataverse. By exposing your F&O tables as virtual entities in Dataverse, you can utilize the highly robust Dataverse connector to trigger automation exactly when data changes.
In Dynamics 365 F&O, navigate to System administration and ensure Dataverse integration and virtual entities are enabled for the specific target table you want to monitor.
Open Power Automate, click on 'Create', select 'Automated cloud flow', and search for the Microsoft Dataverse connector.
Choose the trigger 'When a row is added, modified or deleted'. Select 'Modified' as the change type and pick your F&O virtual table from the dropdown menu.
To prevent the flow from running on every single modification to the record, click 'Show advanced options' and enter the logical name of the specific column in the 'Column filter' field. The flow will now only trigger when that specific value changes.

Consult the Microsoft Power Automate Community for Table-Specific Support
If your specific table does not support virtual entities or data events, you should consult Power Automate experts for specialized workarounds.
Looking for a Reliable and Free Office Suite? Try WPS Office
While Power Automate and Dynamics 365 handle your complex enterprise workflows, you still need a fast, reliable, and highly compatible suite for your daily document processing. WPS Office provides an all-in-one solution for handling spreadsheets, documents, and presentations natively compatible with Microsoft formats, without the heavy subscription fees.
- 1. Download the installer: Visit the official WPS Office website and download the free version for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen prompts to complete the installation in minutes.
- 3. Open your Microsoft files: Launch WPS Office and seamlessly open your existing Word, Excel, and PowerPoint files without any formatting loss.

Frequently Asked Questions
What is the difference between business events and data events in Dynamics 365 F&O?
Business events are triggered by specific business logic or completed processes (like an invoice being successfully posted), whereas data events are triggered directly by basic database operations (Create, Read, Update, Delete) on tables, such as a single field value changing.
Can I trigger a Power Automate flow only when a specific field value changes?
Yes. By using the Dataverse connector and virtual tables, you can use the 'When a row is added, modified or deleted' trigger and specify column filters to ensure the flow only runs when that designated field is modified.
Why doesn't the native F&O connector show my table for data events?
Not all tables are natively exposed for data events in the legacy connector. You may need to enable Dataverse integration, expose the target table as a virtual entity, or consult the Power Automate community for workarounds specific to that entity structure.




