I have a part customization where our application developer created a new tab to add UD field to. One user (myselfđ) seems to have all kinds of trouble with the new customization.
After starting E10 and opening the part form the new tab in the customization is there. I close the part form and move on to other tasks. Epicor is still open and at a later time I need to open the part form again. This time I the new tab is not visible. To add to the puzzle if I do the same test in our test and development environments (different servers) the tab is there when I open the form the second time but I only see part of the customization - almost like it is a version or two behind from the latest saved customization.
We have determined it only happens to me (of courseâŚ) so my pc must have something cached somewhere. I have cleared my client cache for all of the environments with no luck getting the customization to open consistently.
Except for clearing the client cache, can anyone point me in a direction where I could look to correct this.
We started versioning every Customization because of such things like xyz_PartEntry_19.3.13
Make sure you do a hard cache cleanup by deleting the C:\ProgramData\Epicor folder for your instance. The Clear Cache Button within the Epicor Menu seems not to be doing a great job, ever.
Subsequent launches of Part Entry are done the same exact way (i.e. via the same exact menu). And not through a favorite, the history list, or an âOpen with âŚâ context menu?
Try purging your personalizations for that form. And not just the one related to the specific customization, but all of them.
Something that would be interesting to see, would be to do a simple personalization to the âbad formâ (the 2nd time its launched), and exit the form. Then go into Personalization purge and see when that form was last updated. Was the personalization for the desired customization updated, or another one?
And FWIW - I always change the title bar of customized forms to include the customization number.
Interesting. We are currently on 10.2.200.10.
First I thought it was related to the fact that I access multiple databases on one server that can have different customizationâs loaded. While I still think that is an issue, my theory fell apart when I also were having issues on our production server (physical box, one db only).
I followed @hkeric.wci suggestion and renamed by Epicor folder in ProgramData and that allowed for a new folder and files to be created when I logged into our production environment again. My customization seems to open consistently in live now.
I did some review of the files sitting in the Customization and CustomDLLs folder. I am suspecting there is a cleaning process that is not happening even if I clear the client cache or a new customization is applied to the company. We are also multi company and there could be something between an all company vs individual companies customization. We have two companies running this particular part customization and one company that does not that use an all company customization.
I am probably one of the few that bounce back and forth between live, test and development environments all day long testing customizations in different stages and then right now different versions as we get ready to start testing 10.2.300. Hence I am the only one we know this is happening to.
@kfierce - Iâm seeing the same on a Sales Order Entry customization. When I first open the form after clearing cache (I donât have any personalizations), I get the current version. When I close and re-open, I get an older version.
We have a scheduled task that runs on everyoneâs machine that attempts to clear out the cache every 5 minutes as long as they donât currently have a session open. It has alleviated much of this problem.
Iâve seen this recently with doing development on handhelds, made a change to the menu and one login the menu is there, then the next time itâs gone. This was in the context of running through the data collection menu. Logging out of the E10 completely and back in fixed it. I agrees it does sound like a caching issue.
I am just going to assume that the âClear Cacheâ button within Epicor (Under Main Menu) probably fails due to some permissions behind the scenes. No different then when you open Epicor, you canât delete the Folder or some DLLs within that path. So Exiting out of Epicor and Deleting those Cache folder is the only way.
They also do recommend you use a Shared Cache Directory, like UserShares â But I donât see how that can help if User has Epicor open you wonât be able to delete it anyways as an Admin Deploy it to every Desktop or a mini C# App .exe
IDEA
I guess you could create a ClearCache.bat file that kills the Epicor Process and Clears the Cache for your Users and then launches epicor.exe again - where they have to login
Or Version your Customizations, which means Personalizations are Lost.
Also FYI they do not share the Cache between Servers. But they do Between Instances. Meaning if all your Servers are on MYSERVER and you have E10_Pilot, E10_Test, E10_Dev - it would be shared, if you are in a VM Environment and VM Like Setup it wouldnât⌠But it hasnât stopped the Issue.
We are tossing around the idea of a bat file that will clear the C:\ProgramData\Epicor folder each time you log into Epicor. I first thought it was related to multiple instances on one server but the theory broke when I had it happen in live. I am curious to know if the fix in 10.2.300.10 as reference above will fix the issue. I have a test environment with one instance setup that I will try to re-produce the issue.
This is a longstanding issue that was finally found and corrected in 10.2.300.10 and 10.2.200.23. I have requested that we also patch older versions.
The issue is caused by mismanagement of the Customization in regards to âAll Companyâ vs âCompany Specificâ during the first time per session form load - All Company Customization are incorrectly stored as Company Specific. Subsequent form loads correctly look for the All Company cached version but depending on some complex usage patterns may load the correct version or an older version.
I know this is old but weâve just hit this, seemingly out of nowhere, on 10.2.400.
Iâve cleared the cache, deleted the â%programdata%\Epicorâ folder and uplifted the customisation to a new name but the problem persists on every machine we open, close and reopen the forms on
So far weâve spotted it on our CustomerEntry and SalesOrderEntry forms but weâve only just realised that this is there underlying issue of several other intermittent problems our users were reporting so on Monday Iâm going to check other commonly used forms.
This could have been happening for a while but most users may not notice theyâre on an uncustomised screen or may not even close/re-open screens each session so who knows
I donât suppose anybody else has seen this recently?
Deploy it to every Desktop or a mini C# App .exe
