Forum Discussion
- Login as admin
- Navigate to Administration > Variables
- Search for the "Aras.MetadataService.Salt" Variable
- Increment this value by 1 whenever you want to push a change to your clients
- e.g. 0 > 1 > 2 > 3 > etc.
- Similar to the value in the web.config, you should use whole numbers without '.' or '-'
- Save, Unlock, and Close this Variable
- neil_lindberg5 years agoCreator III
Hello, Chris,
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.
Thanks,
Neil
- neil_lindberg5 years agoCreator III
I can't even find this variable. - julien_dufrenne_ansys_com3 years agoIdeator II
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.
- angela3 years agoCatalyst II
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?