Crm Portals Dynamics 365 How To Use Customer
Depending on the audience that the portal is geared toward (such as whether it’s for customers, business partners, or internal team members), a Dynamics 365 portal can allow people to get support for issues, search knowledge guides and how-to guides, collaborateNormally I’d tell you to go ahead and read this crm tip of the day which explains that you need to enable Entity Change Tracking. But what if you need to bypass this caching mechanism?A Dynamics 365 portal provides your audience an online location to communicate and collaborate. When it comes to Liquid fetchxml, whenever Dynamics 365 Portals executes a query it will cache the result of that query. Unlock the keys to excellent customer service.To deliver optimal performance Dynamics 365 Portals do a great job in caching data. Learn all about how to use Customer Self-Service Portals in Microsoft Dynamics 365 for Customer Service. Self Service Access: In Dynamics, there are advanced customizations to pull in content from the existing Dynamics 365 data to give the user self-service.
How it worksIn order to bypass the caching, it’s important to understand how caching works in portals. So here’s how we fixed it. Custom development / actions done in RetrieveMultiple plugins In a recent project, it was the last bit that was giving us trouble. You’re On Prem with an old version (scary, right). We offer Enterprise CRM, ERP solutions powered by Dynamics 365 for clients. I can think of a couple of reasons why Change Tracking might not fit your needs:ERBrains, a leading Microsoft Dynamics 365 Gold Certified partner in India.
This means that the condition won’t affect the expected result, but it will ensure that your query does not get stuck in the cache-zone.Disclaimer: I do not recommend to bypass the cache. In the Code block below, we’ve added a criteria that will ensure the query to be different every second:This condition always evaluates to true as the createdon field will always have a date in the past. You can easily do this in Liquid FetchXml by applying a ‘fake’ filter condition on the createdon field. That way, the next time an identical request comes in, the portal knows it doesn’t need to ask CRM again, because it still has that data in memory.So the solution in bypassing this, is simply ensuring that your query is unique.
The article above merely illustrated how caching can be bypassed when needed.
0 kommentar(er)
