[#3996] - Filter values in visualize.js are cumbersome to work with

Category:
Bug report
Priority:
Normal
Status:
New
Project: Severity:
Minor
Resolution:
Open
Component: Reproducibility:
Always
Assigned to:
0

Trying to pass filter values in visulize.js is very cumbersome here are some of the pain points I've experience whilst evaluating this tool:

- Using reports server ad-hoc report builder, all filters are renamed internally and there is no indication at all about this. I.e. Create a filter on field 'brand' and visualize.js simply just does not filter on params: {'brand': ['Brand Name']}. The name had changed to 'brand_1', no way to tell this from either reports server or visualize js.
- If I pass invalid filters (like 'brand' in case above) there is no error, warning, log, etc
- If I pass a filter value that matches 0 rows then all rows are returned, totally unexpected behaviour

Adding filter value validation errors or messages to the visualize.js returned report would greatly improve usability of filters.

v6.0
guido.tapia's picture
Joined: Dec 4 2014 - 8:52pm
Last seen: 4 years 5 months ago
Feedback
randomness