Skip to main content

Setup Dataverse Connectivity with Dynamics 365 Business Central - Part 2

 Introduction:

In my previous blog, I discussed on what is Microsoft Dataverse and how to setup Dataverse Connectivity with Business Central.


In this blog, I will be attempting to share my experience on fine-tuning various parameters  involved in Business Central integration to Dataverse provided in connector 

Pre-requisites:

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

Books & References:

Demonstration:

1. Dataverse Connection Setup:
For any setups related to Dataverse Connectivity the first step is you go to Dataverse Connection Setup
You search for Dataverse Connection Setup


All the setups related to Dataverse Connection Setup are in the actions of the Dataverse Connection Setup


2.  Connection Actiongroup:
The actions in the Connection Actiongroup are mentioned as follows -

Assisted Setup -  Takes you to the Assisted Setup if the Setup is not enabled.
Test Connection - Runs the Test Connection with the parameter already setup.
Use Certificate Authentication - Use the OAuth2 Service to Service Authentication Connectivity for Integration. When clicked on the Use Certificate Authentication, a dialog box opens similar to

3. Integration Actiongroup:
The actions in the Integration Actiongroup are mentioned as follows -

Couple Salespersons - Shows the list of Users in Dataverse mapped to Salespersons in Business Central. This is done only when the model type is User and not Team. 
However this action is relevant to Dynamics 365 Sales Integration which will be done in the upcoming blogs.
In Salesperson Purchaser List

Add Coupled Users to Team - Adds Coupled User to owning Team. Ideally this is used when you would like to move from single user ownership to team ownership.
Redeploy Integration Solution - This actions deploys the Dataverse Integration solution in Dynamics 365 CRM. 
Integration Solutions - You can also see the Integration Solution deployed to Dynamics 365 CRM. 


Integration User Roles - Shows the Dataverse Integration User Roles. This shows the list of roles assigned to Integration User. This roles are assigned to single user.

Owning Team Roles - Shows the Dataverse Integration Team Roles assigned to the Team. These role are assigned to Team Roles.

Dataverse Integration User - Shows the Dataverse Integration User in Dynamics 365 CRM.


Dataverse Owning Team - Shows the Dataverse Integration Owning Team in Dynamics 365 CRM

Integration Table Mappings - Integration Table Mappings shows the Entities from Dynamics 365 Business Central that will be mapped to Dynamics 365 CRM.

You can set the Table Filter by clicking on Table Filter and you will get the Filter Page. 
You can set the Table Filter on the Dynamics 365 Integration Table Filter and when you click on the Integration Filter Page the filter Page appears as follows

Integration Table Fields Mapping
You can also map the Fields that you want as a part of integration.
It involves fields to Fields Mapping, Direction, Transaction Rule, Not Null etc.
You can go here by going from Integration Mappings > Fields 

Coupling and Uncoupling Records -
Coupling: The process of linking the data between Business Central and Dynamics 365 CRM based upon field matching criteria
Uncoupling: The process of unlinking the data between Business Central and Dynamics 365 CRM.
To couple the records in Business Central, go to Dataverse Connection Setup > Integration Table Mapping > Match-Based Coupling.

You can select if you want to Sync records after Coupling and Create New Record if Unable to match on the basis of matching criteria. Also, you can fields for matching criteria by enabling Match on field.

Incase of  update conflicts, you can select the resolution method.

To Uncouple records go to Dataverse Connection Setup > Integration Table Mappings > Uncoupling

Upon Uncoupling, you will get the a confirmation message if the coupling is stop be stopped and that it will no longer synchronize those records.
After confirming the Uncoupling records, the Integration Synchronization Jobs shows the list of Uncoupled record so far.

For failed Uncoupling records, you will get the exact error. You will get the uncoupled records as follows.
You can manually go to that specific record and uncouple.

Conclusion:

This blog explains in detail how Dataverse Connection Setup  works in Business Central.
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