ArchiveUser
7 years agoQrew Captain
Overriding the 5 dynamic filter constraint
tl;dr: I understand that there's no way to change the 5 filter constraint on QB reports through the front end. Has anyone tried to do this through script?
The handful of ways I tried to do this and failed are as follows:
1) Altering the "maxFacets" global variable that appears in the ?a=viewbuild pages - this allows you to stop seeing the "Maximum number of filters selected" warning but still won't allow you to add anything else.
2) Updating the options for the "qb.columnChooser" jQuery UI widget factory plugin - changed the "maxDestItems" property to have a limit of 10 instead of "maxFacets" - this allows you to actually apply more than 5 filters, but they aren't applied/don't appear once you display the report.
3) Using the FormData API to pass in additional <li> elements on the ?a=viewbuild pages - this has the same effect as #2 on this list
4) On the actual report page, you can construct your own filters using functionality from QB.Faceting object. This works, but it's a lot of work and custom code. I was hoping to just piggyback on what already exists in QB to make this work.
At this point, my curiosity is killing me so any feedback is greatly appreciated. Thank you!
The handful of ways I tried to do this and failed are as follows:
1) Altering the "maxFacets" global variable that appears in the ?a=viewbuild pages - this allows you to stop seeing the "Maximum number of filters selected" warning but still won't allow you to add anything else.
2) Updating the options for the "qb.columnChooser" jQuery UI widget factory plugin - changed the "maxDestItems" property to have a limit of 10 instead of "maxFacets" - this allows you to actually apply more than 5 filters, but they aren't applied/don't appear once you display the report.
3) Using the FormData API to pass in additional <li> elements on the ?a=viewbuild pages - this has the same effect as #2 on this list
4) On the actual report page, you can construct your own filters using functionality from QB.Faceting object. This works, but it's a lot of work and custom code. I was hoping to just piggyback on what already exists in QB to make this work.
At this point, my curiosity is killing me so any feedback is greatly appreciated. Thank you!