asked on December 13, 2024
Hello,
I had a question about how a value filter is supposed to work. In a local CSV file(https://jsfiddle.net/flexmonster/k518ztum/) when I apply a value filter, it filters the values and updates all levels of the pivot where the less aggregated values always sum to the rolled up row above. For example in the attached csv_file_sum.png, I applied the filter of "sum of price" greater than 40(csv_file_filter.png). The aggregate of the color values equal the Accessories value of 3452 as I would expect.
When I use a API source like https://jsfiddle.net/flexmonster/j1c6rd24/ this is not the same. For example in API_sum.png I applied a filter(API_filter.png) of "sum of Price" greater than 3000 but the sum of the two Category values do not equal the above aggregated "Red" value on line 5. The sum of Cars and Components is 953,140 while the above column shows 956,564. Is this expected? Or should the cell value for "red"/"Australia be 953,140? I would have expected the latter. It appears that the API source doesn't update the aggregated cells like the CSV data source does.
Thanks,
Brian
edit:
Looking at this more I suspect the API source for that example is just sending the wrong values and the client is displaying whatever is provided?
⋅ 5 days ago
Hello, Brian!
Thank you for reaching out to us.
Our Dev team needs some time to check the described filtering behavior on our side. We will get back to you with the update soon.
Answering your question, "Looking at this more, I suspect the API source for that example is just sending the wrong values, and the client is displaying whatever is provided?" - yes, you're right. With custom data source API, Flexmonster just shows the values provided by the backend.
In our case, there are two filters applied to the slice: value filter for Category and selection filter for Country. It seems that the subtotal values haven't been updated after applying the second filter.
In this context, it'd be helpful for us to know if you are working with your own custom data source API implementation or using our Flexmonster Data Server as DLL.
Looking forward to hearing from you.
Kind regards,
Solomiia
⋅ 4 days ago
Hello, Brian!
Thank you for giving us some time.
Kindly note that our team will need more thorough research to determine whether we can fix the detailed filtering behavior when a value filter is used along with another one.
Before we proceed with the research, could you please let us know if you are using Flexmonster Data Server as DLL or developing your own implementation of custom data source API? This information would help us greatly.
Looking forward to hearing your feedback.
Kind regards,
Solomiia
⋅ 4 days ago
Solomiia,
I am using my own implementation of the custom data source API. I was using a demo provided on the flexmonster website here https://jsfiddle.net/flexmonster/j1c6rd24/ which uses
dataSource: {
type: "api",
url: "https://olap.flexmonster.com:9500",
index: "fm-product-sales"
},
It appears the behavior I described occurs in that demo. I was trying to figure out if that is a bug in the frontend code or the backend. Here(https://jsfiddle.net/xzpfet97/7/) is an example configured correctly using your demo where the values don't add up correctly(see picture).
If this is a bug in whatever is serving "https://olap.flexmonster.com:9500", I would need to fix my own custom implementation of the API(which I suspect is the case) since I also have the same bug implemented. But if the bug is on the frontend, then I wouldn't need to do anything.
Thanks,
Brian
⋅ 3 days ago
Hello, Brian!
Thank you for your feedback.
We confirm that the discussed filtering behavior is part of the backend functionality.
Since you work with your own custom data source API implementation, the filtering logic would need to be adjusted on your server.
Hope you will find our answer helpful.
Kind regards,
Solomiia