Power Platform Community Forum Thread Details

Hi,

What are the prerequisites for using "When a row is added, modified or deleted" trigger in Power Automate when connected to a Dataverse Virtual Table? For some reason, I am unable to get my configurations to work. Here is the approach I have tried:

I have created a new solution inside a Power Platform Environment in which I have the role as System Administrator.
I then created a new table from a connector - from a Sharepoint List - which creates a "Virtual Table" in the solution. I have the rights to create, update and delete records from the Sharepoint List in question.
I created a new Security Role - to grant users "user-level permissions for create, read, write and delete on the "Callback Registration Table". I then assigned myself to this newly created role.
I added a "Virtual Entity Metadata Table" to the solution - connected it to the new virtual table and set all external messages scopes to yes. I.e. added, modified, deleted and "includes data in changed fields for the update message.
I have created a flow inside the solution - connected to Dataverse via my organizational account which has "System Admin" role in the connected Power Platform environment. The flow uses the "When a row is added, modified or deleted" trigger with a subsequent action which is simply set to a delay timer. I just want to ensure that the actual trigger itself is triggered whenever the Virtual Table is updated via propagation from the underlying Sharepoint list.

I am aware that I could trigger the flow from the underlying Sharepoint list instead, but unfortunately that is not my goal here. I am trying to better understand the underlying requirements/prerequisites that dictate whether or not the Dataverse trigger in Power Automate is triggered or not. The flow checker in Power Automate gives me no errors after I have added the Virtual Entity Metadata table and given myself user-level permissions for the "Callback Registration Table" in the Power Platform Environment.

However, regardless of these configurations, the flow is unable to detect new records being added to the virtual table (initiated by me when I add or modify records in the underlying Sharepoint list). When testing the flow, it just runs - waiting for a signal, allthough I can see that the records in the Virtual Tables are being CUD.

I have managed to get the trigger to work in a Prod Environment for a virtual table created from a table in Dynamics 365 Fin&Ops, so I know that it is possible to get the trigger to work with Virtual Tables, I just do not understand which configurations that are required to achieve it.

Any help would be much obligued!

Categories: