Sync Master Data on Dynamics NAV / Dynamics 365 BC

As a Business Consultant, you might have received a business requirement to sync Master Data between different fiscal companies. It is common when we are implementing an ERP on a Group of companies.

If the ERP to implement is Dynamics NAV / Dynamics 365 BC it is frequent as a first approach, to follow one of the three options:

• Create a customization to enable this automation (Extension on D 365 BC)

• Adopt an ISV solution that includes this functionality (There are some in the market usually under the umbrella name Intercompany)

• Select the tables that you want to share between the different companies and change the property DataPerCompany to “No” on the Development Environment and this table will be unique for all the companies of that database (Only on Dynamics NAV or D365BC On Prem).

When starting to detail the business requirement for an End Customer, it is easy to face difficulties! Blocking Examples:

• The second option (ISV solution) will have a considerable footprint on the database. Usually these ISV solutions cover more than only Sync Master Data and a lot the times, the related cost of the solution is not competitive

• The third option (DataPerCompany=’No’) is not the best as some data of some tables can maybe not be completely the same

• The third option (DataPerCompany=’No’) is not applicable because there are more than one database (having for example different localisations).

So as a partner, we direct frequently to the first option. We completely control this way of implementing, we have developers available with the proper skills and the customer receives a custom-made solution for their requirement.

Let’s be disruptive! The Microsoft Business Applications is not only Dynamics NAV / D365BC anymore. It includes the Power Platform and the Microsoft Power Automate (Ex Microsoft Flow) could be the right piece for this requirement.

Some Advantages to consider:

• Microsoft Power Automate is cloud based, ready, easy to use and friendly for Key User / Super User (No/Low Coding)

• The cost is effective and the footprint is minor.

Short Step by Step to implement:

1. Create a new Service with NAVUserPassword Authentication (If using Dynamics NAV or D365BC On Prem). Verify some pre-requisites:

a) To run a new service with Credential Type = NAVUserPassword a certificate should be installed. To install the certificate, follow the link https://docs.microsoft.com/en-us/dynamics-nav/walkthrough--implementing-security-certificates-in-a-test-environment

b) The Odata Service tab is mandatory.

2. Create a new User on Dynamics NAV or D365 BC for being used by Microsoft Power Automate

3. Access to Microsoft Power Automate with an O365 account and Create a new Connection on Microsoft Power Automate

a) https://us.flow.microsoft.com/en-us/, access Settings > Connections.

b) New Connection, Filter by NAV / Business Central and select your option. Dynamics NAV is shown as in Preview.

c) OData Feed URL with Syntax: http://[DNSNameAzureVirtualMachine]:[Odata_Port]/[NAV_ServiceName_with_N AVUserPassword]/Odata/

d) Username (User with NAVUserPassword)

e) A new connection should be created to each different Dynamics NAV / Business Central database/company.

f) The same BC / NAV user can be used for all the different connections.

4. Create New Flow

a) To create a new flow, select My Flows.

b) If you try to create a new Flow from blank, there is no option to select NAV Action or Trigger. To work around it, you should select to import one. Please contact me, if needed one example to import. After importing, the NAV action and triggers become available.

Example: Sync CoA between two different companies in two different NAV databases

Flow yourself!!!

You are very welcome to comment or feedback.