asked on August 30, 2019
When using column chart in version 2.6.15 with big data set you might get warning: "Data set is too big to be displayed on the chart. Data set will be cut off to the amount fitting into the chart."
Same data set in version 2.7.12-1 ends up in error:
flexmonster.full.js:39106 Uncaught TypeError: Cannot read property 'Et' of undefined
at a3N.rM (flexmonster.full.js:39106)
at a3N.p0 (flexmonster.full.js:39411)
at a3N.Mca (flexmonster.full.js:38753)
at a3N.Na (flexmonster.full.js:38637)
at flexmonster.full.js:36250
at Function.n1x.load (flexmonster.full.js:7380)
at P5S.xN (flexmonster.full.js:36239)
at P5S.rL (flexmonster.full.js:36206)
at flexmonster.full.js:36066
a3N.rM @ flexmonster.full.js:39106
a3N.p0 @ flexmonster.full.js:39411
a3N.Mca @ flexmonster.full.js:38753
a3N.Na @ flexmonster.full.js:38637
(anonymous) @ flexmonster.full.js:36250
n1x.load @ flexmonster.full.js:7380
P5S.xN @ flexmonster.full.js:36239
P5S.rL @ flexmonster.full.js:36206
(anonymous) @ flexmonster.full.js:36066
requestAnimationFrame (async)
q50.requestAnimationFrame @ flexmonster.full.js:1808
P5S.Na @ flexmonster.full.js:36064
P5S.vQ @ flexmonster.full.js:36098
(anonymous) @ flexmonster.full.js:36198
k4.dispatch @ flexmonster.full.js:956
k4.Da @ flexmonster.full.js:981
I0V.Hda @ flexmonster.full.js:5781
(anonymous) @ flexmonster.full.js:5775
requestAnimationFrame (async)
q50.requestAnimationFrame @ flexmonster.full.js:1808
I0V.Jna @ flexmonster.full.js:5772
I0V.c0V.WL @ flexmonster.full.js:5795
⋅ September 2, 2019
Hello, Toni,
Thank you for writing to us.
We have not managed to reproduce the issue on our end: when the data set is too big, the pop-up message appears without any errors.
Our team kindly suggests updating to the latest version 2.7.13 of Flexmonster.
Please let us know if this helps to resolve the issue.
If the error continues to occur after updating, could you please provide a dummy data sample where the issue is reproducible?
This will greatly help our team to understand the problem better.
Waiting for your reply.
Best Regards,
Vera
⋅ September 3, 2019
Updated to 2.7.13 and I still get an error, but a little different one:
flexmonster.full.js:39134 Uncaught TypeError: Cannot read property 'Gt' of undefined
at a5I.tM (flexmonster.full.js:39134)
at a5I.q0 (flexmonster.full.js:39449)
at a5I.Mca (flexmonster.full.js:38781)
at a5I.Ma (flexmonster.full.js:38665)
at flexmonster.full.js:36121
at Function.o2B.load (flexmonster.full.js:7403)
at W9A.AN (flexmonster.full.js:36110)
at W9A.cJ (flexmonster.full.js:36104)
at T8.cJ (flexmonster.full.js:58794)
at Object.S3.showCharts (flexmonster.full.js:59255)
at FlexmonsterToolbar.push../node_modules/flexmonster/flexmonster.full.js.FlexmonsterToolbar.chartsHandler (flexmonster.full.js:129505)
at HTMLAnchorElement.<anonymous> (flexmonster.full.js:130954)
⋅ September 3, 2019
Only Pie Chart is working and all the other charts just show blank screen and the above error. I exported the JSON and loaded the same file on jsfiddle example, but I was unable to reproduce the bug there.
⋅ September 3, 2019
The error is raising from FlexmonsterToolbar.prototype.chartsHandler functions last row this.pivot.showCharts(a, b) where a = 'column' and b = false.
It's hard for me to debug more since the code is minified.
⋅ September 3, 2019
OK. Tried other versions too and this error rises in release 2.7.7 and it is in every release after that. 2.7.6 works OK, but had other issues.
⋅ September 4, 2019
Hello, Toni,
Thank you for reaching out to us.
Our team has tried different ways to reproduce the issue but to no avail.
In order for our development team to provide the right solution, a sample is needed.
Could you please provide us with dummy data with which the error occurs and the Flexmonster report configuration, or access to the environment where the issue is reproducible?
Any sensitive information can be sent via email.
We are looking forward to hearing from you.
Best Regards,
Vera
⋅ September 16, 2019
I'm also having trouble reproducing this error in simplified solution. :/
⋅ September 16, 2019
Hello, Toni,
Thank you for getting back to us.
Could you please provide temporary access to the environment where the issue is reproducible so our team can run the necessary tests?
Any sensitive information can be sent via email.
This will greatly help us to solve the problem.
Waiting for your response.
Best Regards,
Vera
⋅ September 18, 2019
Updated to latest flexmonster 12.7.14 and also updated react from 16.8.6 to 16.9.0 and got rid of the issues.
⋅ September 18, 2019
Hello, Toni,
Thank you for the update.
We are glad to hear that the issue is resolved.
You are welcome to contact us in case of questions.
Best Regards,
Vera
