With the information you presented here could I modify the Item Type > Method to add an "OnAfterSave" event that pointed to a Method that works as an auto-increment of this value? Also, would it make sense to only do this if the method you've added or modified were JS/Client-side?
If you wouldn't mind could I get a sample of how to get at that variable inside a C#, Server Side method? I'm going to try right now. Will post if I get it figured out.
In Innovator 9.3 Release Notes, I see that:
Introduced a Variable Item "Aras.Client.MetadataService.Url.Salt" that can be used to force the metadata cache to reload. By increasing the value of the variable by 1, the end users will refresh the metadata cache the next time they log in.
This post and the solution provided by Chris were intended for Innovator 11. I don´t know if the variable is still used or required in Innovator 12+.
Since I use Innovator 12 I never had trouble with cache problems. I only change the web.config counter in case of codetree modifications. That´s it.
Only scenario that can lead to trouble is if user stored the wrong link to an Innovator instance that contain X-salt value or some tokens. This is a constant pain, case users like to bookmark the Innovator link and often don´t read the hints I gave them in the introduction email, to not "star" the link but to add it manually.
How is your experience?
25 days ago I wrote this sentence: "Since I use Innovator 12 I never had trouble with cache problems."
This smug sentence aged like milk. Cause there is one client side scenario where I right now constantly face caching problems.
Let´s assume we have a regular custom ItemType with Form, Lifecycle and a few custom CUI elements. The ItemType and it´s components are only accessible for a certain "Identity" user group.
When a new user shall access this ItemType, I just add the user to the Identity and ask the user to restart Innovator.
After restart the user can access the ItemType. Everything works, but not the CUI elements. They just don´t appear. But CUI elements will work on the next day (!) or when user use browser incognito mode.
Does anyone one know how to improve cache update when using CUI elements? I don´t want that admins have to update web.config counter each time we add a user to "something".
Have you seen similar behavior in your Innovator? I am still using Innovator 12, not sure if Aras already has improved it.