Skip to main content
Solved

Error "Undefined: KPI Container is not defined"

  • Sep 11, 2026 12:27 PM UTC
  • 18 replies
  • 454 views
  • Translate All

rkenna
Captain II
Forum|alt.badge.img+5

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

Best answer by rkenna

​@Manikanta Dhulipudi ​@asullivanNAW and ​@tkapuenene36, the member I ran into this issue on were on 2025R2 with no real changes to their system… it seems to just have randomly showed up.

 

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.
View original

18 replies

Forum|alt.badge.img+11
  • Captain II
  • Sep 11, 2026 12:46 PM UTC

​@rkenna 

Have you got any mobile app customisations for the screen?

Translate

rkenna
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • Sep 11, 2026 12:50 PM UTC

​@aiwan, the mobile app is not used for this site, and no customization projects on the screen that are causing this.

Translate

Forum|alt.badge.img+11
  • Captain II
  • Sep 11, 2026 12:51 PM UTC

​@rkenna 

 

No problem, was throwing a wildcard out there anyway.

 

Could you please share the trace? And do you have a multitenant setup?

 

Translate

rkenna
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • Sep 11, 2026 4:59 PM UTC

Thanks! 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

Translate

Forum|alt.badge.img+11
  • Captain II
  • Sep 11, 2026 8:20 PM UTC

Can you turn the request profiler on and see what is logged there when that error is thrown?

Translate

  • Freshman I
  • Sep 15, 2026 2:35 PM UTC

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.

Translate

bwhite49
Captain II
Forum|alt.badge.img+12
  • Captain II
  • Sep 17, 2026 1:46 PM UTC

We have 3 or 4 customers getting this error. It’s frustrating for everyone as we can’t explain why it’s happening. 

Translate

rkenna
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • Sep 17, 2026 2:01 PM UTC

Glad 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). 

  1. Navigate to Apply Updates (SM203510) and perform a Reset Caches.
  2. In the same Apply Updates (SM203510) screen, select Restart Application.
  3. Clear your browser cache and browsing history.
  4. 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

Translate

bwhite49
Captain II
Forum|alt.badge.img+12
  • Captain II
  • Sep 17, 2026 2:08 PM UTC

Glad 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). 

  1. Navigate to Apply Updates (SM203510) and perform a Reset Caches.
  2. In the same Apply Updates (SM203510) screen, select Restart Application.
  3. Clear your browser cache and browsing history.
  4. 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.

Translate

bwhite49
Captain II
Forum|alt.badge.img+12
  • Captain II
  • Sep 17, 2026 2:13 PM UTC

Actually, we did not try number 4. We’ll look into that, thanks!

Translate

rkenna
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • Sep 21, 2026 6:56 PM UTC

It seems the proposed solution above did not resolve the issue as it is still taking place. I am thinking this is an Acumatica Bug.

Translate

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. 

Translate

Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+16

​@rkenna ​@bwhite49 Any Help on this error?

Translate

  • Jr Varsity I
  • Sep 24, 2026 9:17 AM UTC

I am also Experience this error and my client is on 25R2.

Translate

rkenna
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • Answer
  • Sep 24, 2026 11:51 AM UTC

​@Manikanta Dhulipudi ​@asullivanNAW and ​@tkapuenene36, the member I ran into this issue on were on 2025R2 with no real changes to their system… it seems to just have randomly showed up.

 

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.
Translate

rkenna
Captain II
Forum|alt.badge.img+5
  • Author
  • Captain II
  • Sep 30, 2026 12:15 PM UTC

Just confirming that step 3 is the key above to the error being resolved.

 

Cheers,

RJ

Translate

Yes, several users have performed step 3 and it seems to be resolved. 

Translate

Everyone, over the weekend users reported that clearing browser cache and history did not correct the issue for them, switched to Chrome and issue persisted, cleared cache etc and issue persisted.  I was able replicate for Acumatica and provide logs.  Steps:  user has dashboard as home page, dashboard load time signification, user clicks on another workspace and selection without opening new tab.   This can intermittently result in the error.   My first attempt at this process replicated issue, I got the message 10 times before I was able to click on trace for logs. After clearing browser cache, it hasn’t replicated. 

Provided logs to Acumatica and their response ‘this is known issue and they are working on a resolution.  No confirmed release version for fix.’   I have removed the dashboard as a home page to help with this error.   For users that have reported this the clear browser cache and history has fixed the problem, this weekend a user I believe to have previously reported the issue and taken steps about a month ago to correct. 

Translate