Virtual entity is a custom entity that has fields containing data read from an external data source, a feature released in Dynamics 365 version 9.
With virtual entities you connect directly to external data source, and data is displayed at runtime, rather than stored in CRM database, as with “normal” entities. The data source can be the SQL server of an ERP system, price list, foreign currency rate of exchange, client’s credit limit vs credit used, outstanding amount for unpaid invoices, and stock levels.
Virtual entity feature is promoted as new and easier way to integrate data from external sources, with no need for full development cycle. This is partially true as the data source has to offer an OData v4 endpoint, for which you do need developers to create these custom endpoints. A solution Dynamics Objects provides in the form of cloud web-service that converts data from SQL database and from Excel spreadsheet to formatted ODATA v4 endpoint. With Dynamics Objects web-service for virtual entities, everyone can now display data from external SQL database and Excel spreadsheet. All you need to do is to configure the entity and enter the connection parameters in Virtual Entity Data Source.
Virtual Entity Web-service licensing is different to any other software license, encouraging re-sellers to pay yearly subscription and resell the service as many times as they can, and hence significantly reduce the cost to end-users.
For data sources other than SQL & Excel, we provide FREE of charge conversion to ODATA v4 endpoint, at no extra cost, if we are provided with access to the data source.
Try Virtual Entity Web Service for free
There is no solution to import to CRM. To try Virtual Server Web-services, you need to configure CRM to read from data source, and create the virtual entity, as per the instructions available on our website.
Hi Khadim
In reply:
* How does your web service fulfill that requirement?
If your datasource has GUID, you point us to the GUID field and we create the records with this GUID. Every time the ist is refreshed, the same record in CRM will have the GUID as in datasource. If you do not provide GUID in datasource, we will create random GUID but it will be different every time
* Do you have a mechanism to provide the same Guid for specific records every time?
if the GUID is not in the datasource our generated GUID is random number and is different every time you refresh the list
* Are we able to use virtual entity based entity records for lookups then?
Yes. Read our other post on the benefits of having GUID in datasource as not only you can have a look up to same VE record, but also you can add notes & activities
One of the requirement for using virtual entity feature is to have ODATA v4 service to return a Guid.
* How does your web service fulfill that requirement?
* Do you have a mechanism to provide the same Guid for specific records every time?
* Are we able to use virtual entity based entity records for lookups then?
Great article. I just got to know about Virtual Entity. Sounds similar to Salesforce Connect. You can actually use a third party solution like Hybrid Data Pipeline to produce OData from a database.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Hi Khadim
In reply:
* How does your web service fulfill that requirement?
If your datasource has GUID, you point us to the GUID field and we create the records with this GUID. Every time the ist is refreshed, the same record in CRM will have the GUID as in datasource. If you do not provide GUID in datasource, we will create random GUID but it will be different every time
* Do you have a mechanism to provide the same Guid for specific records every time?
if the GUID is not in the datasource our generated GUID is random number and is different every time you refresh the list
* Are we able to use virtual entity based entity records for lookups then?
Yes. Read our other post on the benefits of having GUID in datasource as not only you can have a look up to same VE record, but also you can add notes & activities
Hello,
One of the requirement for using virtual entity feature is to have ODATA v4 service to return a Guid.
* How does your web service fulfill that requirement?
* Do you have a mechanism to provide the same Guid for specific records every time?
* Are we able to use virtual entity based entity records for lookups then?
Great article. I just got to know about Virtual Entity. Sounds similar to Salesforce Connect. You can actually use a third party solution likeHybrid Data Pipeline to produce OData from a database.
Awesome post .. Keep up the good job.
Thanks