Filter Widget working opposite
Hi,
I have created a floor plan with a rest service in Portal Experience Builder. The portal version is 10.9.1. The rest service has 3 group layers for each floor. Each group layer consists of other feature layers such as printers, floor spaces, locked spaces. The rest service was later used to create a Web Map. The "locked spaces" feature layer has a field called "locked space" and it has two attributes/values, "Active shooter" and "Locked for Technology".
My main goal here is to display "active shooter" and "Locked for technology" with toggle option. The idea is to show the regular floor plan with all other features, and I want to display "Active shooter" and "Locked for technology" on top of regular floor plan but with the toggle option.
To achieve that, I used 2 separate filter widgets for each attribute (active shooter and locked for technology) as you can see in below picture.
For filter, I didn't create any data view, but I used SQL query for each filter accordingly. Now the issue is filter widget is behaving opposite to what it should do. When both toggles are off, both attributes (active shooter and locked space for technology) are being displayed. And when both filters are on, they disappear. See below picture.
I am not sure what I am doing wrong here. Any insights will be appreciated.
Thanks.
Every option in the SQL builder has a negative equivalent, so if you aren't getting what you want from 'is' try 'is not'.
You could also use the turn on automatically option to reverse the feel of the filter.
Ok, I think I figured out the problem. Because you are using two separate filter widgets on the same data, they are fighting each other. Try putting filters in the same Filter Widget and using the OR connector.
Like you suggested, I tried filters using "OR" but it still behaves the same way. Anyway, I kinda got what I wanted but it's not ideal.
So, the issue I am facing is, in experience builder you can't just turn off the feature layer and then use it again for filter widget. Over here, the feature layer for Locked spaces is "on" before applying any filters. If I keep it "on", I'll face the problem like I mentioned in my initial post. For solution, I added one more filter called "Turn off" which turns off the "locked space" feature layer visibly. See below.
Now If I apply both other filters, it works like I wanted it to, but this solution is not ideal.
I wanted something like picture 2 ideally but without "Turn off" filter.
