You’re offline. This is a read only version of the page.
Hello, I was wondering if there was any way to disable all caching for the portal? Possibly through a site setting or something like that?
Liquid like this will not display updated data on the portal: {% assign account = entities.account[ID] %}. Sometimes it displays updated data instantly, other times hours. For more complex pages that require a FetchXML query, I just include a condition: created = now, and that forces Adxstudio to not use the cached value. I would like to avoid doing this on all my pages if possible.
I am running my portal in the cloud, so I don't have access to the actual project, and the web notifications do not work at all (never could get it working..),
Any tips?
*This post is locked for comments
I'm having a lot of problems with WebNotification... I'm getting an error 401 when the Plugin is trying to access the WebNotification page.
Have you ever faced something similar?
I'm surprised to read explanation above.
We started on v8.1, moved on to 8.2.
We had multiple calls with Microsoft about caching issues.
The only solution they had for us was the old school Web Notifications.
This is what we use still today. Even in our test environment, which is v8.3
The portal is currently on 8.3.x. Thank you for sending that manual invalidation link; it works much faster than rebooting the entire portal.
Is it possible for me to look at the back-end configuration, or is this something Microsoft can only do?
Hi, it would be good to know exactly what version of the portal you are running, you can determine this by navigating to http://portalurl.domain.com/_services/about
With the CRM Portals (v8.1.x)/Dynamics 365 portal (v8.2.x - v8.3.x) there is not a way to disable the cache. There is the built-in cache invalidation that uses a service bus behind the scenes to send invalidation messages to the portal. Alternatively there is also a web notifications solution in which you can manually configure the old style of notifications where the CRM async service basically sends a HTTP POST to the portal. This old way is deprecated and ultimately should not be used and actually will be completely removed in a future version.
In my experience with the portals the service bus method does work very well if it is working. If it is not working then something in the backend configuration for your instance is likely an issue and you should open a support ticket to have it resolved.
If you are on the latest version of Dynamics 365 portals - v8.3.x then you also have a way of manually invalidating the cache when you are signed into the portal with the Administrator role. You can navigate to http://portalurl.domain.com/_services/about and at the bottom should be a Tool with a button called "Clear Cache". This will invalidate the entire cache of the portal so that it will re-retrieve any data from the Dynamics 365 instance on the next call.
There is a screenshot of that interface in this post - http://colinvermander.com/2017/07/20/dynamics-365-portals-upgrade-to-july-2017-update-v8-3/
If you are using the legacy Adxstudio portals then yes there is a way to change to an uncached service context but it is not advisable at all as the performance impact is quiet significant. Check out the following thread and specifically the replies from Gabe.
https://community.adxstudio.com/forums/adxstudio-portals/f8cfabfa-59c7-4cfb-b4ab-ee850ffd4324
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (