Tried in Kinetic (browser) and wasn’t able to replicate. I recorded the process so you could review it. Now I’m going to try the Smart Client. Stay tuned.
I was able to get the “Sorry, Something Went Wrong…” error when doing this with the Smart Client - this environment is on 2023.2.5. It only appeared on one of the three screens, and when I closed and opened them again, there was no Business Layer Exception. I’m wondering if the fact that I’m logged in to all 3 sessions as the same user makes a difference? I’m going to test that now.
No that’s all you need chris you did it. Do you see strings now in the smart client?
On order entry or whatever form you were doign?
No no, that’s exactly what happens to me, one screen gets a “sorry something went wrong” and the others load, but now they others have {{strings}} errors.
I wasn’t seeing the {{ Strings }} error when I reopened Order Entry after receiving the Business Layer Exception. I’m testing now with different user accounts just in case that changes anything.
Could be just version specific I guess man. Because the support agents also say they can’t replicate the {{strings}} issue we have. But you have it too which must be from a different issue or something.
you should see the strings error on the other sessions that managed to open.
You nailed it Logged in as (3) different users, followed the instructions and got a BL Exception on one, the other 2 opened OK, but with {{Strings}} showing. What’s odd is I closed all 3 windows, re-opened Order Entry, and now the {{ Strings }} are gone.
Make sure you are doing ctrl + alt + i in all sessions on all forms before repeating the test.
LETS GOOOOO CHRIS
body seems unclear!
What version are you on?
I’m gonna try it again. I’m still logged in to all 3 sessions.
Testing this in 2023.2.5
1 Like
I was able to reproduce it again. It’s resolving itself, though, which may be a result of changes in 2023.2.5 - we’re on 2023.1 in Live. I’m hesitant to do this in production during the day, so I may test it this weekend to confirm it doesn’t self-resolve. Appreciate the help! Let me know how your session with support goes.
1 Like
so It looks like they’ve made it better in the other versions.
Do you have a 2023.2.5 box to test on?
No.
@aball … any way we could ask you to also test this?
Utah, you’re not going to believe this…for any user who is seeing the {{ strings }} error, go into User Account Maintenance and set the language to English (United States), and format culture to English/United States. Save and have the user log out and log back in. It’s worked for every one of our users who were getting this error. I just DMT-updated everyone, so hopefully this error is a thing of the past! Appreciate all your help getting through this.
1 Like