Making your Business Central Connected Flows a part of a managed release, using Environment Variables

Dynamics 365 Business Central

The blog article discusses different ways to synchronize data from Power Platform/Dataverse to Business Central systems, including Out of the Box (OOB) integration, custom APIs, and using Power Automate flows.
The OOB integration requires systems to share the same base currency, which may not always be possible, leading to the use of custom APIs or Power Automate flows.
Using the BC Connector in Power Automate introduces complexity during releases as it requires specifying the environment and company, necessitating manual edits each time the flow is released as part of a solution.
Environment variables in Power Platform can address this issue by creating variables for the environment name and Company ID, allowing for a smoother release process.
To set up the Environment variables, create two variables of type text in the PP/DV Development environment and input the required values like the Environment Name and Company ID.
When setting up the BC Connector in the flow, use the Environment variables created to streamline the process and avoid manual edits during releases.
Renaming connection references and using them consistently across environments can help maintain a tidy set of connections when using the BC Connector.
It is important to note that when using filters in OData endpoints, the field names may differ from those specified in the page inspector, so it is essential to verify the correct field names for filtering purposes.

Registered users can view the full text for FREE!