2 Replies Latest reply on Jan 15, 2019 4:55 AM by Ross Helenius

    Boolean filters not interpreted the same in URL parameter and JS API

    Ross Helenius

      We use a few boolean filters and depending on the situation pass it as a URL parameter or though the API. When used in the URL it looks like all lowercase true/false is used, workbooks default to True/False. This creates overhead in managing different boolean values when passing.

       

      Just curious if others deal with this. One approach that doesn't seem great is to alias all workbook values to lowercase, however this is a lot of maintenance and I am concerned it would alter the integrity of a true boolean performance and domain wise.

       

      Edit:

      I should add for a little more clarity, if it is passed as an option for the viz before initialization in gets passed to the URL, where if you apply it after load in applyfilterasync it will use the upper case values.