Hi,
We have a strange problem that cropped up only recently when we changed one of the queries in our portal to be based on FetchXML instead of LINQ.
Even though our web notifications are firing, and the Portal should be invalidating its cache, the results stay stale until a manual refresh is done by calling Cache.axd?message=invalidateAll
Steps to reproduce:
- Access a view that is built using a FetchXML result set
- Go make a change to some piece of data that appears in that view (from the portal or from CRM doesn't seem to matter which)
- Go back to the view, observe that the data is stale and showing the old state
I don't understand why this is happening or how it's possible. It's almost as if the automatic web notification is insufficient to refresh the cache entirely when using FetchXML.
I have confirmed that when I access a part of the application that's using LINQ and make a change to the data , the portal cache is being invalidated correctly and the data is updated the next time I refresh the browser.
Environment: Dynamics CRM 2015 (on prem), portal built using ADXStudio Portals 7.0.13
Thanks for any help
