Also, you’re right I wasn’t able to reproduce the issue 100% of the time but I talked to my coworker yesterday and when I demoed the steps to him, I replicated the {{strings}} problem in that menu (No user had a personnalization at that time). Since the cache was stored with {{strings}}, every user that had the same language and same personnalization as that cache would see the {{strings}} when opening the menu
Okay @vingeance@spaceage@Stevensi1018 , I updated my sysconfig, recycled the app pool, and ran conversion 191 as well after that and now I don’t have the {{Strings}} issue when I follow the replication steps I posted. BUT I still get a business error on the two other forms I open. PLease note that I have english set as a language for everyone as well- which I think setting a language is necessary to avoid the {{strings}} issue as @spaceage pointed out.
That, to me, is still worthy of a PRB right? Like we should be able to open 3 forms at once, right?
Additionally, I am still trying to get them to acknowledge the {{strings}} as a PRB so that they can assign some sort of action plan to reduce the number of people affected by it. Whether that’s setting that sysconfig parameter to false for us during conversions/upgrades, making the language field mandatory, and/or adding steps in the guides to tell us to run converstions after making personalizations/customizations… idk just something.
Definitely. Especially since you don’t have to be logged in as the same user in those sessions to trigger the error. That (in my mind) replicates different users in the system activating the same form at the same time…not an unusual situation at all, especially at the beginning of the day.
Also, while the {{strings}} thing is fixed, the two screens that got errors in the smart client are hosed. I can’t open that form anymore using menu search, I can’t go back to the home page, it’s like it’s all messed up. I have to close and re-open the smart client… At least the {{strings}} thing isn’t happening, but this isn’t that much better.
I found an easy fix for those who have the {{ strings.XXXX }} issue. This is not a permanent solution, but it is quicker and a lot easier than reprocessing Conversion Workbench task.
Just open Application Studio for the program having the issue. It will clear the program cache in the database for all languages.
Do note that it will only work for those who have KineticUseFileSystemNotDB flag set to FALSE.
The ( CTRL + ALT + i ) should work for those who have KineticUseFileSystemNotDB flag set to TRUE, as it deletes the MetaUI cache files.
Update
No news from Epicor support for 3 weeks. I kindly asked, only once per week, if they could give me an update on the case. No response.
I escalated the case today.
Who could take 5 minutes to test the steps I provided to Epicor? (it does take only 5 minutes if you already have the following prerequisites).
Prerequisites :
Epicor environment greater or equal to 2021.1.7 (below steps were done in a 2023.1.12 demo env.)
Microsoft Edge web browser
Google Chrome web browser
Make sure KineticUseFileSystemNotDB flag is set to FALSE (confirmed by Epicor in another case)
At least 2 languages installed (in this test, English United States and French Canada were used)
Launch Epicor in your Microsoft Edge browser
Connect using “epicor” user
Click on the bottom left button (user settings)
Select Company “EPIC06 | Epicor Education” and Site “Main”
Select English/United States language
In the Main Menu, select Service Management / Project Management / General Operations
To the right of Job Entry program, click the star icon
Click the Save button to add Job Entry to your favorites
In the Menu, select “Favorites”, then click on Favorites folder.
You should see Job Entry in your favorites. Open it (the Job Entry program).
Click the top-right icon (to the right of the search icon), then select Application Studio.
Application Studio should have opened in another tab. Close the tab. Note: This Application Studio step is required to clear the database cache for the Job Entry program.
Launch another Epicor in your Google Chrome browser
Connect using “epicor” user
Click on the bottom left button (user settings)
Select français/Canada language
Refresh the page to make sure the language is fully loaded
Note: The following steps require to be fast. Please see screenshot below. The objective is to simulate users in different languages who would open the same form at the same time. The easiest way is having your Microsoft Edge browser occupying the half-left of your screen, and the Google Chrome browser occupying the half-right of your screen. Have your Job Entry in your favorites ready.
Click on the Job Entry favorites program in your Google Chrome session.
As soon as possible, click on the Job Entry favorites program in your Microsoft Edge session.
Problem : You will either get “Sorry, something went wrong”, or {{ strings.XXXX }}, or both issues.
I am pretty saddened by this. Cause I saw it at insights. Like with my own eyes, and so did the 50 other people in the class. Multiple times throughout the week. so why they are not acknowledging any of it is kind of a mystery.
Vague right now, but you did it @vingeance. We did it.
Thanks a ton to everyone who hopped on here intermittently and tried out everyone’s advice and steps to replicate.
I am hoping that maybe those out there that are dealing with this, but just going along with the data fix route and slew of “try this” suggestions that they are receiving as a recommended solution can get a true fix once and for all.
