In my previous blog post I described how the naming convention for flows with a Common Data Service (current environment) trigger can be enforced with Power Automate flow, and could be extended for other trigger types like Recurrence and Request based on a Switch action. If flows with the CDS(ce) trigger are the only “target”, there is a simplified flow that can do the job.
Here is the…
Continue Reading StefanS365’s Article on their blog
Power Automate the enforcement of naming convention on flows with CDS(ce) trigger: Revisited – There’s Something About Dynamics 365
Posted by In my previous blog post I described how the naming convention for flows with a Common Data Service (current environment) trigger can be enforced with Power Automate flow, and could be extended for other trigger types like Recurrence and Request based on a Switch action.
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