The Microsoft Power Platform is more than the sum of its parts. Connect them together—and to Microsoft 365, Dynamics 365, Azure, and hundreds of other apps—and build end-to-end business solutions.
Want to be more effective and efficient in your business? Check SSW's Power Platform consulting page.
When creating workflows in Dynamics developers take for granted when a solution file is moved across environments, things just work. To achieve the same with Flows we need to make sure that when connecting to Dynamics using the Common Data Service connector, we in fact connect with Common Data Service (Current Environment) connector. This connector is environmentally aware and will immediately work when the parent solution is deployed to another environment, it doesn't require any post-deployment steps.
Dynamics has come a long way since the early days and now sits under Power Platform. So why not take advantage of all the capabilities to make Dynamics sing. Prior to Power Automate and Azure Functions, a Dynamics developer would use a combination of Workflows (synchronous and asynchronous) and Plugins to extend the system.
When creating a Flow that connects to CRM, Flow gives you the choice of:
- Dynamics 365
- Common Data Service
- Common Data Service (Current Environment)
Out of the box, any user with the correct licence can create environments. If you are managing Power Platform and would like to restrict environment creation and management only to admin then change the global settings:
Using groups and service accounts is a common best practice in the Power Platform world.
When working with Power Automate flows, there are instances where you need to use or compare the time in your flow, by default, it is set to UTC.
However, there are situations where using your local timezone might be more appropriate, especially for tasks or events that are specific to a particular region. It's important to choose the appropriate timezone based on the context and requirements of your task or system.
- <imageEmbed alt="Image" size="medium" showBorder={true} figureEmbed={ { preset: "default", figure: "The power of Power Automate", shouldDisplay: true } } src="/uploads/rules/automation-tools/power-automate-logo.png" />
In the old days, if employees wanted something automated they would have to call up the development team and go through a long bureaucratic process to get a traditional API built. These days, there are heaps of tools that make this easy, quick and simple.
If you're not versioning Power Platform Apps before each deployment, you could be setting yourself up for a world of confusion. A lack of versioning can lead to difficulties in tracking changes, resolving issues, and managing the development lifecycle.
The solution is straightforward: Add a version to your Power Platform Apps before every deploy. This way, you can keep track of what functionality is contained in a particular solution release.
Whether you're an expert or just getting started, working towards gaining a new certification is a worthwhile investment.
Microsoft provides numerous certifications and training options to help you:
- Learn new skills
- Fill technical knowledge gaps
- Boost your productivity
- Prove your competence
- Do you create a Solution and use "Current Environment" when creating Flow for Dynamics?
- Do you take advantage of Power Automate and Azure Functions in your Dynamics solutions?
- Do you use the Common Data Service connector instead of the Dynamics 365 connector when using flows?
- Do you control who can create and manage Power Platform environments using the admin centre?
- Power Automate Flows - Do you use groups and service accounts?
- Do you know how to use correct timezone in your Power Automate flows?
- Do you use the right tool to automate your processes?
- Do you version Power Platform solutions before deploying?
- Do you know the relevant Power Platform certifications and associated exams?