You’re offline. This is a read only version of the page.
Hi guys,
I am developing a new project and I have some questions and doubts about the number of necessary records to store in Dynamics CRM.
The project is mostly around clients-sells-sells details-products and so on. But the tricky part here is that the client has more than 20 000 000 records to import to CRM online. The records will be imported from various integrations services and webservices. The goal is to analyze the data by using Power BI and create some reports. And finally, create some marketing campaigns that depend on the client's size. One requirement from the client is that the fields that are not created on CRM platform must be on read-only mode.
My experience so far tells me that CRM is not perfect when we are working with a LOT of records. So I remembered that Microsoft introduced virtual entities on the latest version of CRM. My question here is: should I use the virtual entities on my project? Can I create an external Database to store the data that I really don't need on CRM? In terms of performance, there is a big difference between using or not using virtual entities? If I introduce this feature to the client I really need to convince them to buy an Azure Database as sass. Is it Worth it? Can you share your experience on this feature?
Regards!!
*This post is locked for comments
I have the same question (0)
We are also thinking about it but not exactly, as this is not really Mastering the data concept. We are retiring few legacy so we ll migrate those data & we ll master them.
The external system which will exist & continue mastering the data will make use of this virtual entity. That’s the purpose too.
Your case study is interesting & definitely you have to do pilot, no one knows what your entire system and data relationships.
A month of trial in Azure can help you with that pilot.
#1
Community Member
2
#2
Christoph Pock
1
Share
Report
All responses (
Answers (
