Get Free Trial
Get Free Trial

Custom Datasource API - Expanding All Data and Layouts Bug

posted on September 27th, 2021

Re-Open
Henry asked on September 27, 2021

Hello,
 
We believe we have found a bug with the expandAllData api when coupled with the Custom Datasource API. If it helps, we are currently on version 2.9.5.

In the following jsFiddle, we have a report that contains two rows that are initially collapsed.

  1. When we click on the "Expand All Data" button, the rows are expanded as desired.
  2. When we change the layout to "Flat form," the layout loads as expected
  3. When we change the layout back to "Compact form," we get a "Uncaught TypeError: g is undefined" error in the console.
    • The same error actually occurs regardless of the number of rows we have. For example, if we remove the country row, and go through the steps again, we get the same error.
    • We were unable to reproduce the error when the data source is json.
  4. jsFiddle

 
Please let us know if there is something wrong with the jsFiddle or if we can provide any additional information!
 
Kind regards,
Henry
 

3 answers

Public
Mykhailo Halaida Mykhailo Halaida ⋅ Flexmonster ⋅ September 28, 2021

Hi Henry,
 
Thank you for reporting this.
 
Our team will take a look at this issue and provide a fix with our upcoming release on ETA Oct 18th.
 
Please let us know if there is anything else we can help you with in the meantime.
 
Best regards,
Mykhailo

Public
Mykhailo Halaida Mykhailo Halaida ⋅ Flexmonster ⋅ October 19, 2021

Hi Henry,

 
The issue with switching views when using the custom data source API was fixed.
 
The fix is available in the 2.9.10 version of Flexmonster: https://www.flexmonster.com/release-notes/.
 
You are welcome to update the component. Here is our updating to the latest version tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
 
Please let us know if everything works fine for you.
 
Best regards,
Mykhailo

Public
Henry ⋅ October 19, 2021

Hi Mykhailo,
 
Upgrading to 2.9.10 looks to have fixed the issue. Much thanks to you and the team!
 
Kind regards,
Henry

Please login or Register to Submit Answer