Identify all the cloudflows on a particular entity along with its messages
Learning dynamics 365, Azure and Power Platform
Search for a command to run...
Learning dynamics 365, Azure and Power Platform
No comments yet. Be the first to comment.
Currently there is no straight forward way to open a canvas apps from the ribbon button unlike the custom page that can be opened using the Xrm.Navigation.navigateTo(pageInput,navigationOptions).then(successCallback,errorCallback);Refer : navigateTo ...
This is a preview feature ; works for flows that are part of solution. The flow run history is now stored in the table 'flowrun' and can be queried to get the history. Enabling the functionality :To enable this navigate to https://admin.powerplatfor...
What is Dataverse AI Functions Dataverse Provides built in AI Functions that are preconfigured. They are ready to use and do not require any data for training. They help in streamlining and improving the process Different available AI Functions ...
Tag parameter is a savior when it comes to situation where a particular plugin execution needs to be skipped. Scenario - A custom api creates contact and also performs execution of certain logic. Also, there is a plugin that executes similar logic wh...
The easiest way to identify the flows that trigger on a particular entity with its messages is to run a SQL query using the sql4cds tool in the xrmtoolbox.
The table that has the information is callback registration, querying the call back registration table provides information about the modern flow/ cloud flow guid.
We can then join it with workflow table to retrieve all the valid information.
SELECT
CR.entityname,
CR.messagename,
WF.name AS workflow_name
FROM
workflow AS WF
INNER JOIN
callbackregistration AS CR ON WF.workflowid = CR.name
GROUP BY
CR.entityname,CR.messagename,WF.name
ORDER BY
CR.entityname,CR.messagename;
CR.entityname: Represents the name of the entity from the callbackregistration table.
CR.messagename: Represents the name of the message from the callbackregistration table.
WF.name AS workflow_name: Represents the name of the workflow from the workflow
It joins the workflow table (aliased as WF) with the callbackregistration table (aliased as CR) using the condition WF.workflowid = CR.name. This condition ensures that records are matched based on the equality of the workflowid column in the workflow table and the name column in the callbackregistration table.
Then Groups the results based on the columns we need/specify and orders the results.
