Using Virtual Tables in Dynamics 365 CRM to show sync errors with Business Central

Introduction

In the ever-evolving world of business, efficient data management is crucial. One tool that has proven invaluable in this regard is Microsoft’s Dynamics 365 CRM. This blog post is intended for anyone interested in understanding how virtual tables can be used to display syncing errors between Dynamics 365 CRM and Business Central.

What are Virtual Tables?

Virtual tables in Dynamics 365 CRM are a type of metadata. They allow external data sources to appear within the system as if they were part of the CRM database. This feature provides seamless integration and interaction with external data, enhancing the overall user experience.

Syncing Errors between Dynamics 365 CRM and Business Central

Syncing data between Dynamics 365 CRM and Business Central is a common practice in many businesses. However, this process is not always flawless. Errors may occur due to various reasons such as network issues, incompatible data formats, or software bugs. These errors can disrupt business operations and lead to significant losses if not addressed promptly. To help users navigate these syncs and errors, we can hep them by displaying the errors directly in CRM.

Using Virtual Tables to Show Syncing Errors

Virtual tables can be a powerful tool for diagnosing and resolving syncing errors. By setting up a virtual table, you can display the error data directly within Dynamics 365 CRM. To illustrate the power of virtual tables, let’s consider a case where a business was experiencing frequent syncing errors between Dynamics 365 CRM and Business Central. The errors were causing significant disruptions to their operations. By setting up a virtual table, they were able to display the error data directly within Dynamics 365 CRM. This allowed them to diagnose and resolve the issues promptly, resulting in improved operational efficiency.

Below we show how we used virtual tables to make this possible
1. A prerequisite is access to the integration errors Business Central. Therefor we needed to create an api to make the table which stores the errors, public
2. We create a virtual table in crm via the Business Central Configuration app

3. An extra field has been created in the integration error table with the guid of the crm record the error originates from. This information will then also be available in the virtual table in crm, so we can make a mapping and relate an error to an actual record in crm.

4. We create a field on the account table in crm, where we store the guid of the record. We make this field a key for the account table, which is needed to make a relationship with mapping between the virtual table and the crm account table

5. Now we can add a subgrid on the account form to our virtual table with integration errors, which filters on the guid of our record

Conclusion

Virtual tables in Dynamics 365 CRM provide a powerful tool for managing and displaying external data. In our case study, we made them very useful for diagnosing and resolving syncing errors between Dynamics 365 CRM and Business Central. By understanding and utilizing this feature, users can significantly enhance their data management capabilities.