Accepted Solutions
Hi Kate, thanks for the clarification, and you are using them correctly.
For the Filter widget, the user could add multiple filters, but you can only add one in the List widget - that's the current design. Maybe we could evaluate and discuss if we can enhance it later. If you feel necessary, you could post on the Ideas page or Tech Support to log an ENH issue as well.
However, there could be a workaround if you dig this user interface. You can utilize the Filter widget as you configured above, change the Arrangement style to "Icon", and then put it onto the right corner of the List widget. In that way (with some style tweaks), as long as they are using the same layer, the behavior will look quite alike - hope it could help:
@KateRose The SQL Expression Builder inside the List widget provides the full functionality same as the Filter widget, such as the Ask-for-values option, and that's why the doc is linked to the ones in W-Filter. Are you referring to the function that W-Filter can add multiple filter items but W-List can add only one? I have a hard time understanding this - "I only get to build one single query that has to include a value for each attribute with no option to just not include attributes in the query". What do you mean by just including attributes in the query?
Hi Tonghui-
Apologies for my admittedly poor explanation of the issue I'm having! I'll try again 🙂
My feature layer has 40+ features and several fields. Each field only has one attribute value, but the features have different combinations of attributes and null values.
With the W-Filter I can create a filter linked to the W-List that uses the simple SQL clause for each field so that if a feature has that attribute, it will be selected. The attribute source type is "unique". There's no user input, but users are still able to select which attributes to filter for in the W-Filter bar.
I selected the AND option for the filters so that the features can be filtered by one or more attributes
-----------------------------------------------------------------------------------------------------------------------------------------------------
I can not figure out how to replicate this in the W-List. I'm following the same SQL query/filter setup:
but that gives me a single filter for every SQL query
I've tried other filter configurations that require user input, hoping that it would then force selection options, but it ends up being a very non-intuitive process for the user.
For example, this configuration
give me this, which is asking the user to select between the value and All (which is the same thing). It does filter the list correctly but doesn't allow selection of a single or multiple values.
I don't want users to have to fill in fields, as in your example above. I'd like them to just look at a list of attributes/values and select which ones to filter for. Maybe I'm not using the SQL expressions correctly?
thx
Kate
Hi Kate, thanks for the clarification, and you are using them correctly.
For the Filter widget, the user could add multiple filters, but you can only add one in the List widget - that's the current design. Maybe we could evaluate and discuss if we can enhance it later. If you feel necessary, you could post on the Ideas page or Tech Support to log an ENH issue as well.
However, there could be a workaround if you dig this user interface. You can utilize the Filter widget as you configured above, change the Arrangement style to "Icon", and then put it onto the right corner of the List widget. In that way (with some style tweaks), as long as they are using the same layer, the behavior will look quite alike - hope it could help:
