Enforcement of the naming convention, as described in my previous blog post, can be Power Automated. The CDS|Dynamics 365 workflow properties (attributes value) can be used to compose the prefix for the workflow naming.
| Workflow properties | Values | Prefix if true |
| mode | 0 (Background), 1 (Real-time) | RT> |
| ondemand | true, false | OD |
| subprocess | true, false | CW |
| triggeroncreate | true,… |
Continue Reading StefanS365’s Article on their blog
Power Automate the enforcement of naming convention on CDS|Dynamics 365 workflows – There’s Something About Dynamics 365
Posted by Enforcement of the naming convention, as described in my previous blog post, can be Power Automated. The CDS|Dynamics 365 workflow properties (attributes value) can be used to compose the prefix for the workflow naming. Here is the overview of the flow: The List Workflow records will get the unmanaged workflows (category: 0 – classic Common Data Service workflows) from a specific solution.
Blog Syndicated with StefanS365’s Permission
More About This Author
Array
Dyn365CE2 February 2024Validate file input of manually triggered flow with trigger conditions
Dyn365CE25 October 2023Bulk Delete assets in Microsoft Purview via the user interface
Dyn365CE24 October 2023Bulk Delete assets in Microsoft Purview with Power Automate flow
Dyn365CE26 March 2023Populate a dynamic Microsoft Word template in Power Automate flow
