If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

"Uncaught TypeError: Cannot read property" error

Started by robblob, 03 Oct 2019 08:08:27 AM

Previous topic - Next topic

robblob

Curious if anyone else has encountered this error before (attached)?  I've had a report in a production environment for about 2 years and the issue only recently developed from what we can tell.  We are currently on 11.1 R3 in our prod environment, but the report was originally developed not terribly long after 11.0 dropped.

The report utilizes some JS which handles a flyout window from the left hand side of the report which contains all of the prompting.  We use the same JS with other reports that don't experience any issues, but the error seems to be related to the JS and this specific report.  The error occurs when we change tabs, flyout the window, set a prompt, then switch back to the first tab.  After clicking to change tabs, it hesitates and then throws this error. 

We have completely deconstructed the report and slowly rebuilt it while saving and running between iterations.  Everything was fine yesterday, but as soon as we came in today it blew up on the first run.  I'm not sure if there is something with caching that is related to the error or what, but we can't put our finger on it.  Any suggestions?

robblob

Just resolved the issue so wanted to share what it ended up being. 

After the reconstructed report finally blew up with the same error, I started deleting items to try and pin point the issue again.  Turns out, it was the 11.1 visualization causing the error with the JS.  I converted it to an 11.0 vis and no more errors.

Maybe someone here can shed some light on why that may be, but I wanted to follow-up in the event that someone else runs across this down the road.

MFGF

Quote from: robblob on 03 Oct 2019 08:49:26 AM
Just resolved the issue so wanted to share what it ended up being. 

After the reconstructed report finally blew up with the same error, I started deleting items to try and pin point the issue again.  Turns out, it was the 11.1 visualization causing the error with the JS.  I converted it to an 11.0 vis and no more errors.

Maybe someone here can shed some light on why that may be, but I wanted to follow-up in the event that someone else runs across this down the road.

I don't profess to be a javaScript expert, but I do know that the 11.1 visualizations are javaScript based and are rendered client-side in the browser. The 11.0 visualizations are java based and render server-side. My guess is that the 11.1 viz javaScript didn't get along with your code in the report, but that's purely a guess...

Cheers!

MF.
Meep!