Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Can anyone please explains how the Dynamics CRM 2015 caching is working actually in terms of what is being cached on the client side? for example, are the entity views actually being cached or not. Are forms being cached on the client side or not ... etc.
Also how caching is working on server side in terms of requests and responses made by CRM agent clients? What are the rules used by CRM to decide on caching repeated or heavy requests?
Thanks and best regards,
Caching happens on forms not on the views. and its pretty much standard internet explorer/chrome caching or any other .net application. in your custom codes you can make use of caching or control it.
Dynamics does cache as much as it can on both the client and server. The client web resources are cached using the normal http cache and the server uses a custom cache that is internal and not exposed.
read more here : www.develop1.net/.../CRM-Developer-e28098Must-Knowe28099-2-Web-Resource-Caching.aspx
You can also get some helps from here -
Thank you for your response.
I am more interested in the caching of heavy queries data (hundred of thousands of record) done by views, is there any caching occurs during loading the view's data? The caching would be on the SQLServer side or on the CRM backend side?
There is for sure caching on almost each application layer. But yours question seems to be too abstract. Describing particular task or problem would allow to provide more apt answers by experts.
Anyway I don't think CRM was designed for work with "hundred of thousands of record" in one view on client-side. By default CRM limits retrieval by 5000 records and utilizes paging extensively to query only exact data that's need to be presented in UI.
We went from on-prem 2004 CRM to Dynamics CRM. It seems to me that data, not being cached locally, the problem manifest in a number of ways.
I think there are a number of possibilities that could create the above issues for us, but I think the primary one is how data is cached.
Business Applications communities