Do you have two Dynamics 365 environments -- for example, one for sales and one for service -- and wish you could show data from one in the other? With the Dynamics 365 Data Provider solution, you can! The solution allows you to create Virtual Entities tied to an external Dynamics 365 data source and pull in data from any entity.
Out of the box, Dynamics 365 V9 only comes with one data provider for virtual entities - the OData V4 Data Provider. However, it is possible to create a custom data provider with a little bit of custom code. There are a few examples floating around online, but none of them show how to set this up with a practical example (i.e. one that isn't hard-coded). In this post, we'll walk through creating a custom data provider for an Azure Cosmos DB data source.
With the recent release of Dynamics 365 V9, it is now possible to have Virtual Entities. These are entities that are not stored in the CRM database, but rather get their data from an OData API. This allows you to, for example, use on-premises data in Dynamics 365 without having to directly integrate it. Read on to learn how to configure this!