asked on September 14, 2017
I recently tried updated from 2.401 to 2.403. In my pivot I have reportFilters provided both by initial configuration and also via triggered runQuery calls. Now, for some of those (non-date fields it seems, although I'm not sure), the filter doesn't seem to be applied correctly. Instead the field is added to the filter row, but it's not limited at all.
Take a look at the following fiddle which I think demonstrates the issue: https://jsfiddle.net/qbo24wts/
When you click "Run Query," it adds a Country filter, but it has All selected instead of the correct countries.
⋅ September 15, 2017
Hello Jaime,
Thank you for reporting the issue and providing the example.
We are aware of this issue. The fix will be delivered with minor release 2.405, ETA Oct 9. As a temporary workaround, please try changing all letters in filter to lowercase, e.g. replace "Country.[France]" with "country.[france]".
Does it work for you?
Regards,
Tanya
⋅ September 18, 2017
Hi Tanya,
That did work for me. We'll make use of this fix until it is fixed in 2.405.
⋅ September 19, 2017
I just wanted to make sure that your team is aware that this also affects sortOrder. If you don't down-case all of the values in a sortOrder array then that won't work either.
⋅ September 20, 2017
Hello, Jaime,
Thank you for notifying us about sortOrder issue. Our team is already aware of this issue. It will be fixed in minor release 2.405 as well.
Please let me know if you have other questions.
Regards,
Tanya
⋅ October 18, 2017
Hello, Jaime,
I am glad to inform you that the minor release 2.405 is available for download.
The issue with backward compatibility for member unique names was fixed. This fix resolved the following issues:
sortOrder restoration from the report if the member’s unique name contains a capital letter.You are welcome to update the component.
Regards,
Tanya