Skip to main content

Setup Dataverse Connectivity with Dynamics 365 Business Central - Part 1

Introduction:

Dataverse is a single platform where you can store all your data in the cloud and comes API and plugins to connect with the Tables stored.
Dataverse also acts as a Database for Dynamics 365  CRM (Sales, Marketing, Field Service  etc..), PowerApps and Power Platform.


In this blog, I will be attempting to share my experience in connecting Business Central to Dataverse using the out of the box connector provided by Microsoft.

Pre-requisites:

  • Microsoft Dynamics 365 Business Central
  • Microsoft Dataverse
  • Basic understanding of Dataverse and Business Central

Books & References:

Demonstration:

1. Start the Setup Wizard by going to Assisted Setup:
You can search for Assisted Setup > Setup Connection to Dataverse

This will open the Dataverse connection setup wizard. Go ahead and hit Next to proceed.


2. Select the relevant Dataverse environments:
The setup wizard will show you the list of environments available, if you are doing this setup the first time, you won't be seeing the list of environments.

You can add a new Environment by inserting the D365 CRM URL in the textbox.


3. Authenticate as Administrator:
In order to setup the connection successfully, you need to authentication Business Central user to connect to Dataverse using Administrator credentials.

After authenticating with the administration credentials, the Dataverse login screen can be closed and you will see that the User is signed in.

4. Setup the Dataverse Ownership Model:
In Dataverse or CRM the record ownership is set Team or Owner
For Ownership as Team, all the rights of the records is with the company.
For Ownership as Person, you will need to setup ownership for each Sales Person.


After the Dataverse Connection Setup is completed, you have the ability to enable synchronize the entities. You choose if you want to Synchronize the data then can enable the toggle.

After the setup the Dataverse Connection Setup is completed.

5. Test Connection:
To ensure that the Dataverse Connection Setup is completed, run the Test Connection.

You should be getting the Connection Successful message as shown below.

Conclusion:

This blog concludes here on Dataverse Connection Setup in Business Central.
In this next part I will showcasing the details on field mapping, transformation rules, matching criteria and many more points.

For enquiries please email me on olisterr@outlook.com
Thanks.

Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe