You see we had two AOSes that we needed to flush the cache, but could not stop and start the AOSes. The only way I have ever known to flush the AOS is to stop and start it. You may or may not be aware of three menu action items that can be used to flush system data, the AOD, and dictionary. The thing about these though is that they are set to run at "called from" which when ran clear the client cache.
Well the trick is to copy these three menu items, and then change the run from property to server. Now you can launch these menu items, and they will run on the server, therefore clearing the AOD, sys data, and dictionary, causing a refresh.
So the three menu items that you copy (don't change the real deals) are:[Under Menu items > Action]
1. SysFlushAOD
2. SysFlushData
3. SysFlushDictionary
This is a nice little trick that we should all keep in our bags.
*******************
here's a code to flush Axapta Object Cache (AOC) on clients in 3-tier: configuration:xSession::removeAOC();
SysTreeNode::refreshAll();
SysFlushDictionary::doFlush();
SysFlushAOD::doFlush();
xSession::updateAOC();
it may be useful in case you update the application and clients don't "see" the modifications - just bind this to a menuitem and run. thanks to vallys from axforum. AOC is usually found in files %userprofile%\local settings\application data\*.aoc
**************************
