asked on February 22, 2022
Hey Team,
Recently I've updated to the latest version(v2.9.19). While calling getData API, in the response I'm getting extra properties called "r0_full, r1_full ...etc.
So what is the use of "r0_full, r1_full"?
At the same time, Is there any way to remove "r0_full, r1_full ...etc"? because of these new changes, a lot of customized code changes are breaking.
I've mentioned the sample response below.
{
"r0": "2021",
"r0_full": "year.[2021]",
"r1": "a,b",
"r1_full": "city.[a,b]",
"v0": 100,
"v1": 102
}
Even though, the document is not updated with the latest version changes. https://www.flexmonster.com/api/getdata/
Thanks,
Ravi A
⋅ February 23, 2022
Hello, Ravi,
Thank you for writing to us.
The extra properties called "r0_full", "r1_full", etc. were added to provide more possibilities when integrating with third-party charting libraries.
For example, you can get the full path of a particular data point with them. Using this information, you can make your third-party visualizations more interactive, for instance, by making the chart drillable. The extra properties were introduced together with new API calls for expanding/collapsing specific cells programmatically: expandCell(), collapseCell(), drillDownCell(), and drillUpCell(). Our team will update the getData() description accordingly.
Still, you can avoid the new properties when processing the getData() output:
A possible solution is to use the headers from the meta-object and select only the r0, r1, etc. data types. Please see an example of such provided in the following Support Ticket: https://www.flexmonster.com/question/dont-like-getdata-raw-data-format/#answer-33771.
Please let us know if this helps.
Kind regards,
Vera
⋅ March 10, 2022
Hi Vera Didenko,
This changes is a breaking change for us. it cant be consider as a patch release. it should be released under major or minor release!
since it required to handle and pre-process the pivot data before we use it into our external libraries.
definitely it will lead performance issue in the browser at client side. Please check your other customer also who is using external lib for charts or map.
Note : consider we are dealing with lakhs of data used JSON data source.
⋅ March 10, 2022
Hello, Ravi,
Thank you for your reply.
We hope to make this work together and will do our best to help you move forward with the update process.
As we understood, you would like to remove the extra full-name properties for a smoother and simpler update process.
This can be achieved via a wrapper function that will remove those properties from the getData() output.
Please see the following example we have prepared for you: http://jsfiddle.net/flexmonster/f6v871wx/.
With this approach, you could keep your current customization logic.
We truly hope this helps to resolve the issue.
Please let us know if this works.
Kind regards,
Vera
⋅ March 15, 2022
Thanks for the update!
While moving all the dimensions to columns using the move to columns option, getting cundefined_full.
I'll attach the fiddle link. Clicking on the print button, we can see the result. I've printed the result in the console also.
http://jsfiddle.net/2ym470b5/19/
Thanks
Ravi A
⋅ March 15, 2022
Hello, Ravi,
Thank you for reporting this issue.
Our team will provide the fix to this issue in our upcoming minor release, with the ETA 21st of March.
Feel free to reach out to us if further questions arise in the meantime.
Kind regards,
Vera
⋅ March 21, 2022
Hello, Ravi,
We are happy to inform you that the issue with getData API call when there are only columns in the slice was fixed.
This is available in the latest (2.9.21) version of Flexmonster.
You are welcome to update the component.
Please let us know if the fix works well for you.
Looking forward to your feedback.
Kind regards,
Vera
⋅ April 1, 2022
Hello, Ravi,
Our team is wondering if the getData API call fix works fine for you.
Did the update fix the cundefined_full properties for you?
Looking forward to your reply.
Kind regards,
Vera