What could be the reason for pxserialchart is not defined error?

​@Naveen Boga  Do u have any idea on this?

​@michellew86  Thanks for tagging me here. To be honest, I never seen this issue before.

I am also running into this issue- It is intermittent and occurs when attempting to view Purchase Orders and Sales orders. 

​@tracyn81 Were u able to find out the root cause for this?

One user is getting this randomly.

I’ve got a few users experiencing when drilling from a Dashboard to a GI on Sales Orders or going back to the Dashboard from the GI.

We have a couple of users reporting the same issue, mostly in Purchase Receipts.  They sometimes have to dismiss the message multiple times before it clears.

Also seeing this for some users along with an intermittent KPIContainer is not defined error.  No clue.

Hello everyone, 

I also have a user that is starting to experience the KPIContainer is not defined error, it was intermittent but seems to occurs daily with his morning log-in. 

Has this issue been raised with Acumatica support? 

yes, and as usual, they blame it on customizations.  But only one user was getting the error.

I’m now seeing KPIContainer is not defined errors on 3 different clients and I believe it is all related to some change made in the way Dashboard loading is cached on the local browser. It is especially egregious when users have intermittent internet lag and could occur several minutes after leaving the dashboard and starting to work in completely different screens. Three completely different clients with completely different sites and different customizations all starting to experience this same issue within the last 30 days has to be related to something done outside of the individual systems.

Hi,

I wanted to check if there's already a solution or fix for this. My client is also experiencing the "undefined: KPIContainer is not defined" error message, similar to what's being reported here. It happens intermittently, mostly when navigating to certain screens, and the user has to click OK several times before it clears.

Hi ​@michellew86,

Could you provide information, such as which Acumatica version, which screen it is happening on, steps to recreate, etc. It will helpful information to provide you with a right solution.

Just saw this for the first time. Custom screen.

Build 26.101.0225.1

Opened the screen. Loaded up a record and the error appeared. Unable to reproduce.

I’ve also encountered the KPI Container error in two different client environments, both on version 25R2. Cannot replicate the error on demand as there is no pattern or replicable sequence that triggers the error.

Making a note here, so hopefully Acumatica will address the issue, rather than point to customizations.

We’ve also had one user report the PXSerialChart is not defined error, similar to the original post. The build is 25.201.0213 and it’s happening intermittenty when raising purchase orders. I will raise it with Acumatica support - it seems strange that a few of us have all started experiencing this recently. 

We got the issue on the build : 25.201.0213.6. I raised with Acumatica support too. However Still unable to track it as there were no issue logs created for the error.

Does anyone happen to know if this error is browser based? Or have a current work around?

Acumatica support think it’s probably to do with browser or cache. They asked the user to delete their browser history and try again. I passed that message on and haven’t heard anything back, which might mean it worked, or might mean they haven’t tried it yet! If that doesn’t work you could also try the Reset Cache option under Apply Updates.

​@aspurdle We have cleared the cache and still got the error. We changed the browser too. 

There is another Community thread about the KPIContainer error where Acumatica suggest the following:

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.

​@michellew86 ​@tracyn81 ​@dgodsill97 ​@bmonaghan ​@mhatrick ​@bdale32 ​@klovell2023 ​@bwong91 ​@Zia ​@Django ​@dgower199680 ​@aspurdle ​@Mgonzales86

Thanks to all of you for your community involvement. Please keep creating cases for this issue, as that helps us see trends and drives priority by case volume. Engineering is aware of the issue and is investigating, so I would expect a fix to be forthcoming.

Just a heads up that we are getting more and more of these errors reported in our user base. What started with a single user has now turned into a much more common problem. We are using 24.R2 and I can confirm this issue is not limited to just version 25 and later.