{"id":10624,"date":"2025-04-26T05:47:57","date_gmt":"2025-04-26T05:47:57","guid":{"rendered":"https:\/\/www.aegissofttech.com\/insights\/?p=10624"},"modified":"2025-10-29T11:49:39","modified_gmt":"2025-10-29T11:49:39","slug":"power-automate-detect-dynamics-crm-operations","status":"publish","type":"post","link":"https:\/\/www.aegissofttech.com\/insights\/power-automate-detect-dynamics-crm-operations\/","title":{"rendered":"Create\/Update\/Delete Dynamics CRM Operation in a Power-Automate Flow Dynamically"},"content":{"rendered":"\n

INTRODUCTION<\/strong><\/h2>\n\n\n\n

This quick guide explains an easy and effective way to figure out whether a Dataverse-triggered Power Automate flow is running because of a Create, Update, or Delete<\/strong> action in Microsoft Dynamics 365 CRM Solutions<\/a>. By capturing the sdkmessage<\/em><\/strong> value from the trigger\u2019s output, we can clearly identify what kind of operation started the flow.<\/p>\n\n\n\n

With this method, used frequently by experienced Dynamics 365 CRM consultants<\/a><\/strong>, we can build more intelligent flows that adjust their steps based on the type of change made to a record. It helps reduce the need for multiple separate flows and gives us better control and flexibility when automating business logic.<\/p>\n\n\n\n

STEPS<\/em><\/strong><\/h3>\n\n\n\n

1. To begin with, we create a new Power-Automate cloud flow, setting the Dataverse trigger to \u2013 \u201cWhen a row is added, modified or deleted<\/em>\u201d.<\/p>\n\n\n\n

\"added,<\/figure>\n\n\n\n

2. After naming the flow as per its intended relevance, we set the table name = Accounts in the trigger. We specify that in the case of the UPDATE operation, the flow must trigger only when the name of an Account is updated.<\/p>\n\n\n\n

\"Accounts<\/figure>\n\n\n\n

3. We then initialize a variable named varSdkMessage to triggerOutputs()?[\u2018body\/sdkmessage\u2019]<\/em>,<\/strong> that is, to the SDK Message property of the output body of the above trigger.<\/p>\n\n\n\n

\"triggerOutputs\"<\/figure>\n\n\n\n

4. We save these customizations of the Flow.<\/p>\n\n\n\n

UNIT TESTING<\/strong><\/h2>\n\n\n\n