Hi Community,
Has anyone ever run into this error before on a Sales Order? It seems like it would be from a dashboard maybe considering the site has no container management on it.
Cheers,
RJ Kenna
Solved
Error "Undefined: KPI Container is not defined"
+5Best answer by rkenna
I did the following 2 steps, and 1 User cleared their cache and browsing history, and another did not. The one who did no longer received the error. The one who did not received the error again. Step 3 is critical it seems.
- Navigate to Apply Updates (SM203510) and perform a Reset Caches.
- In the same Apply Updates (SM203510) screen, select Restart Application.
- Clear your browser cache and browsing history.
- If applicable, use the Modern UI for the screens configured on your default home page.
+5
No problem, was throwing a wildcard out there anyway.
Could you please share the trace? And do you have a multitenant setup?
+5Thanks! I am trying to get the trace, but it is random when it comes up. When it does, I will send it. No multi-tenant.
Cheers,
RJ
We upgraded to 2026 R1 recently. Got report from one user he is getting this error on Sales Orders screen. He says clicking OK sometimes clears it but not always.
+12We have 3 or 4 customers getting this error. It’s frustrating for everyone as we can’t explain why it’s happening.
+5Glad I am not the only one. I did reach out to Acumatica, and they gave me these steps. The member has not reported it since, so it is looking like it did the job (so far).
- Navigate to Apply Updates (SM203510) and perform a Reset Caches.
- In the same Apply Updates (SM203510) screen, select Restart Application.
- Clear your browser cache and browsing history.
- If applicable, use the Modern UI for the screens configured on your default home page.
I will respond in the thread if it comes up for them, but this looks like it resolved it.
Cheers,
RJ
+12Glad I am not the only one. I did reach out to Acumatica, and they gave me these steps. The member has not reported it since, so it is looking like it did the job (so far).
- Navigate to Apply Updates (SM203510) and perform a Reset Caches.
- In the same Apply Updates (SM203510) screen, select Restart Application.
- Clear your browser cache and browsing history.
- If applicable, use the Modern UI for the screens configured on your default home page.
I will respond in the thread if it comes up for them, but this looks like it resolved it.
Cheers,
RJ
Thanks, we have one partner where this solution did not work, and it’s not obvious that it worked for the others as there is the intermittent aspect. We'll see… I appreciate the reply.
+12Actually, we did not try number 4. We’ll look into that, thanks!
+5It seems the proposed solution above did not resolve the issue as it is still taking place. I am thinking this is an Acumatica Bug.
I am adding that this is occurring to a 25r2 site also, just completed the steps and waiting for feedback. This is intermittent on that site.
+16
+5
I did the following 2 steps, and 1 User cleared their cache and browsing history, and another did not. The one who did no longer received the error. The one who did not received the error again. Step 3 is critical it seems.
- Navigate to Apply Updates (SM203510) and perform a Reset Caches.
- In the same Apply Updates (SM203510) screen, select Restart Application.
- Clear your browser cache and browsing history.
- If applicable, use the Modern UI for the screens configured on your default home page.
+5Just confirming that step 3 is the key above to the error being resolved.
Cheers,
RJ
Login to the community
No account yet? Create an account
Social Login
Login with your Acumatica accountEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.