asked on October 10, 2024
Hello,
I am using flexmonster with a custom API implementation. I am seeing what I think may be a bug that seems slightly related to the fix for this. When I have a hierarchy and I move a second field into a column and open that field I see a API request that has a filter that looks like the attached filter.txt file. Specifically I think the following is an issue.
"include": [{}]
It seems like it has a filter applied that includes nothing. Is this actually a bug or should I be filtering this out on the backend?
It only seems to happen when I add the field to a column in a existing pivot. If I load the pivot from scratch with the column included, it doesn't seem to send this request. Only when the pivot is already load and I update it via the UI to include the column
Thanks,
Brian
⋅ October 10, 2024
https://drive.google.com/file/d/1y3TMUS4gqpWpaytOTMJqqKGkJ3N6Ambl/view?usp=sharing
Here is an example. You can see when I first add the field as a column, it appears to send an additional request with the empty filter. Once I save the configuration with the field as a column and completely reload the report configuration(rather than updating an existing report) it seems to work fine.
⋅ October 11, 2024
Hello, Brian!
Thank you for reaching out to us.
Our team could not reproduce the described case with the empty include filter sent in the custom data source API requests on our side. Please provide us with the example or modify the following JSFIddle to make the case reproducible: https://jsfiddle.net/flexmonster/Lthd6w32/.
With this information, we'll be able to continue the investigation.
Looking forward to hearing from you.
Kind regards,
Solomiia
⋅ October 14, 2024
Solomiia,
I tried recreating it via the example JSFIddle you provided and I was unable to. I suspect it may be because my dataset is slightly different. For example my hierarchy is two levels deep. Could I provide a sample dataset CSV and report configuration that would allow you to load the dataset that can reproduce the bug.
I also noticed it only occurs when moving the field from row to column. If the field isn't in the pivot and I add it via the fields button, it works just fine.
Let me know if providing the dataset would be benefical and I can send it over.
Thanks,
Brian
⋅ October 15, 2024
Hello, Brian!
Thank you for getting back to us.
Our team would be happy if you provided the report and sample CSV data that we can check. We'll try the provided data and configurations with our custom data source API implementation and let you know if the case is reproducible on our end.
If there is sensitive data in your sample dataset, you are welcome to send everything to our inbox.
Looking forward to hearing from you.
Kind regards,
Solomiia
⋅ October 15, 2024
I sent an email with the sample data/configuration. Thank you for all your help.
⋅ October 17, 2024
Hello, Brian!
Many thanks for supplying the sample data and report.
We could reproduce this behavior on our side. We agree that this inconsistency in requests, depending on how the field is added to columns, may be confusing. Our team will investigate the issue with an empty "include" filter and get back to you with results, ETA Nov 25th.
As a temporary solution, you could adjust the server to handle such requests with an empty "include" filter without an error.
Please let us know if more questions arise.
Best Regards,
Maksym
⋅ November 26, 2024
Hello, Brian!
We are glad to inform you that the issue with an empty include filter sent in the query when a multilevel hierarchy is present in the slice has been fixed. This is available in the 2.9.91 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-91 /
You are welcome to update the component. Here is our guide on upgrading to the latest version: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please let us know if the fix works.
Best regards,
Maksym
⋅ December 5, 2024
Maksym,
Thank you! I confirmed that this is working!
Best,
Brian
⋅ December 6, 2024
Hello, Brian!
Thank you for your feedback.
We are glad that our fix worked for you.
Please let us know if more questions arise.
Best Regards,
Maksym