You’re offline. This is a read only version of the page.
2,761
Is anyone else seeing caching issues with HTML and JavaScript Web Resources in Chrome? Not sure if its Microsoft or Chrome ( 83.0.4103.116) that have introduced a change, but something has definitely changed in about the last week that is affecting the caching of web resources. (The issue is not present on the old Edge, my work PC doesn't have the Chromium version so not sure about that version)
If I make a change to a HTML or JavaScript Web Resource (the latter is referenced from inside a HTML Web Resource) and then Publish (or Publish All), the change is not reflecting through to the User Interface (Unified), I do what I always do and refresh the browser (normal refresh, ctrl+R, or crtl+F5) but the changes are not coming through - they usually would - the only way I can get them to come through is if
Whilst I can get the update to come through from a developer perspective, I am now concerned as to if this will impact our normal users that are using Chrome whenever a change is published.
Hi,
I have not experienced anything like this recently. I am currently using the same Chrome version as you.
You are making changes directly into the system correct? Unmanaged changes?
What type of changes are you doing and not being reflected?
I would assume that if this is occurring in different browsers, the problem could be related to the browser itself and not with Dynamics.
If this is something consistent you can also try to open a case with our team and with some more information we can try to see if helps.
Another small test that you can do is try on Chrome Canary. This normally has a beta version for testers.
Please let me know and I'll try t help.
Share
Report
All responses (
Answers (
