defaulting model condition to on prevents table filter from disabling the condition?

Question

I have a page with a model with a condition that is filterable and on by default with a hard-coded default value. I have added a table to my page, using that model, and a filter on that table that can alter the value of the model’s condition. However, when I use the “Create a 'Filter Off” option’, that condition’s value does not turn off, it just returns back to the default filter value of the model. Is this intentional? Is there a way to disable the condition when the filter option is all/nofilter?

Page 1 / 1

I often find that you have to remove the "Create a ‘Filter Off’ option that is located in the primary filter properties and add a manual source to the filter whose effect is to disactivate the condition. In my experience this has always done the trick.

Rob_Hatch · Answer

I often find that you have to remove the "Create a ‘Filter Off’ option that is located in the primary filter properties and add a manual source to the filter whose effect is to disactivate the condition. In my experience this has always done the trick.

View our Community Site Map

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded