Selecting chat type is not working

Hello.
 
We are using the flexmonster with the latest version (v.2.9.57) and still having issues.
Could you help us ?
The problem occurs in flexmonster when the selected viewType is "charts" (position 0 in the chart list) and the first time another chart type is selected, the event emitter of the output function "reportChange()" is not triggered.
From the 2nd time changed, the event is triggered.
We are passing the json file as example below to flexmonster:
{   "dataSource": {     "type": "json",     "filename": "https://ambiente-7586.qualyexpress.com/audixpress/rest/v2/core/bi/querys/43a1f2a4dc11bb6667b7dfb5f3923f1c40abb7e9"   },   "slice": {     "rows": [       {         "uniqueName": "Posição Heatmap"       }     ],     "columns": [       {         "uniqueName": "[Measures]"       }     ],     "measures": [       {         "uniqueName": "Urgência (ponto extra)",         "aggregation": "sum"       }     ]   },   "options": {     "viewType": "charts"   },   "localization": {     "grid": {       "blankMember": "N/A",       "dateInvalidCaption": "N/A"     }   },   "version": "2.9.57",   "creationDate": "2023-08-14T17:37:10.098Z" }

Dear Nadia Khodakivska.
 
I really appreciate your response, but I still got the same problem reported to you before.
Link JSFiddle: https://jsfiddle.net/bgywh0ve/5/
 
I check your link and put there an event to observe if flexmosters works corretly, I will send you with this message the JS example.
- Firstly when you introduce the code in JSFiddle, flexmoster will start in vertical bar.
- Second step, you need to change to any other kind of chart.
- after that, change to other type of chart, when you change, you have got a message that chart have been updated.
 
The problems only happens if the bar started in the vertical bar and only in first change. We reported you because we need the event emitter works (reportChange), to persistence in our database. If possible we want to share our screen to explain better the problem.
 
Best regards

Hello Nadia.
 
Solved =D
 
We tested the lastest version and the problem did not occur. 
 
Thanks you very much.