Fusion Chart errors
Hi,
A while ago we developed some custom widgets using charts, they were working fine until recently I found out some issues:
- Uncaught (in promise) Error: TypeError: Cannot read properties of undefined (reading 'call')
- Uncaught (in promise) Error: TypeError: h is not a constructor
- Uncaught Error: #90211 ExtensionName Error >> A FusionCharts extension must have a getName API or a name property.
Only information I could find is that it could be a package management issue (maybe related to NPM/Yarn) and that we might need to reset the JS local environment (rebuilding the dependency tree).
Have anyone seen this issue before? wondering if we might need to raise a ticket to fix this... (our application is hosted in the Pega cloud)
Thanks,
-Jose Navas
Accepted Solution
Updated: 2 Mar 2022 13:23 EST
Blue Zone Consulting Partners
US
Pegasystems Inc.
GB
Can you tell us when the charts last worked correctly? Was Pega updated?
Do you see errors relating to using incompatible files or deprecated "register" API of FusionCharts? See fusion docs to know more.
--> Did you install the Map Pack from Pega Market Place?
Please note that the product will be moving away from the use of pzCustomFusionChart and pyAdvancedFusionChart - these are very old non-autogen controls that were originally built to allow customers to custom-render charts for their Pega data using the full FusionCharts library. These controls use legacy chart resize logic, and their parameters can only be configured in IE.
When the Fusioncharts JS library was upgraded for recent 8.x versions, these control were not upgraded to work with the new versions of the library and are considered deprecated.
Can you tell us when the charts last worked correctly? Was Pega updated?
Do you see errors relating to using incompatible files or deprecated "register" API of FusionCharts? See fusion docs to know more.
--> Did you install the Map Pack from Pega Market Place?
Please note that the product will be moving away from the use of pzCustomFusionChart and pyAdvancedFusionChart - these are very old non-autogen controls that were originally built to allow customers to custom-render charts for their Pega data using the full FusionCharts library. These controls use legacy chart resize logic, and their parameters can only be configured in IE.
When the Fusioncharts JS library was upgraded for recent 8.x versions, these control were not upgraded to work with the new versions of the library and are considered deprecated.
Importantly, we have a modern alternative to these controls. Customers can now use the pxChart engine to render custom FusionCharts using a new modern method for custom controls, which allows for modern chart resize logic and customizable parameters across any browser.
Could you please make sure you have the javascript file pyfusioncharts.theme.default • js in your environment and that it is not saved in your custom ruleset? Could this be a caching issue? Are the widgets loading fine in other nodes? If there is a node with an issue, please restart and clear the temp directory so the static content could be regenerated.
Does your chrome debugging show if the issue is due to javascript file. fusioncharts.charts • js? Are you able to do a private edit of it?
Could you run BulkValidateSave activity so the js can be regenerated? ie Perform a private edit of the activity @baseclass • BulkValidateSave from Pega-UIDesign
Pegasystems Inc.
GB
@josenavas can you confirm that you are using the controls mentioned in my previous comment? I have attached instructions for creating a modern custom chart control.
Perhaps these will help you.
Accepted Solution
Updated: 2 Mar 2022 13:23 EST
Blue Zone Consulting Partners
US
@MarijeSchillernthank you. That file with instructions will definitely be useful in the future when we create new charts.
Regarding the original issue, one of our teammates, Alessandro, found an issue caused by the fusioncharts js file. Recently we added a Pega Robot Manager layer as part of the application stack, our guess is that there is some inconsistency between the fusioncharts js versions in Pega-Gadgets and Robotics. So we did a save as from Pega-Gadgets to a upper layer, to override the one in Robotics, that fixed the issue.
Pegasystems Inc.
GB
@josenavas Awesome. Thanks so much for giving us the visibility of how this was put right.
Would you be able to mark one of our responses as 'Accept Solution' so that other forum users can benefit from your work? Thanks!
@MarijeSchillernthank you. That file with instructions will definitely be useful in the future when we create new charts.
Regarding the original issue, one of our teammates, Alessandro, found an issue caused by the fusioncharts js file. Recently we added a Pega Robot Manager layer as part of the application stack, our guess is that there is some inconsistency between the fusioncharts js versions in Pega-Gadgets and Robotics. So we did a save as from Pega-Gadgets to a upper layer, to override the one in Robotics, that fixed the issue.