Need a special offer?Find out if your project fits.
+

updateData() resets the filter defined in the slice

Answered
Jesper Bo Rasmussen asked on August 19, 2019

Hi
As i read the documentation (https://www.flexmonster.com/api/updatedata/) the slice and therefor also the filters, should stay the same when calling updateData(), but as my fiddle below illustrates, the filter is removed.
 
http://jsfiddle.net/jesperra/92htnwbL/
 
Am i doing anything wrong, or is this a bug?
 
Thanks,
Jesper

5 answers

Public
Dmytro Zvazhii Dmytro Zvazhii Flexmonster August 19, 2019

Hello Jesper,
Thank you for writing to us.
 
Yes, you are right. Such behavior does not look correct.
Our dev team needs to spend some time investigating the issue. We will notify you of the results ETA Sep 9.
 
Please let us know in case of any other question.
Regards,
Dmytro

Public
Vera Didenko Vera Didenko Flexmonster September 10, 2019

Hello, Jesper,
 
We are glad to inform you that the issue with optimizing pre-defined filter type was fixed.
 
This is provided in the 2.7.14 version of Flexmonster: https://www.flexmonster.com/release-notes/
 
You are welcome to update the component.
Here is our updating to the latest version guide for assistance: https://www.flexmonster.com/doc/updating-to-the-latest-version/ 
 
Please let us know if everything works.
 
Best Regards,
Vera

Public
Jesper Bo Rasmussen October 9, 2019

Hi
 
I have discovered a new bug.
If flexmonster is initialized without data or with only json-metadata, the filters are not set.
So when loading data later with updateData(), the filters are missing.
This new example illustrates the problem
http://jsfiddle.net/jesperra/o8dmyr6h/
 
Thanks
Jesper

Public
Vera Didenko Vera Didenko Flexmonster October 10, 2019

Hello, Jesper,
 
Thank you for writing to us.
 
We would like to explain that this happens due to the fact that there are no members to exclude when the report is created.
Since the updateData() API call does not reset the slice, the filter is not reapplied.
 
Unfortunately, we don't have the possibility to change the described behavior at the moment.
However, there is a quick and simple workaround:
Our team kindly suggests setting the needed filter via the setFilter() API call after updateData().
 
Please let us know if you have any questions.
 
Best Regards,
Vera

Public
Jesper Bo Rasmussen October 10, 2019

Hi Vera
 
Thanks for the quick reply.
I will look into if that suits our needs, or I have further questions.

Please login or Register to Submit Answer