So, I'm trying to select multiple names however it only allows me to select 1 name. There are times when I can select them but I have to click on the boxes really fast and even when I'm able to select them. The filter does not work properly. Basically, I want the user to select a province, and based on that it should only show the user the names associated with the selected province, and from there they should be allowed to select multiple names. The filter is working for one of my views, however, when I replicate the process for other views (the layer being filtered for each view is the same), I'm only able to select it once. Could you please help @TonghuiMing @@ShengdiZhang @jcarlson?
Accepted Solutions
@TheGamer It seems like the configuration of the Clause set has some logical defects.
In view2, the configuration contains two single clauses; while in view1, it is two clauses within one clause set:
Currently, you could change Filter1's setting to two single clauses, like that of Filter2, as a workaround.
In the meantime, we'll try to fix the problem. Thanks for bringing it up.
@TheGamer Unfortunately, I got the "Create map failed" message, which I believe is due to the fact that the web map used is not shared.
However, based on the sight of your app configuration, I believe what you saw is as expected, because of the two filters "contains the same data being filtered". Once you've filtered the data in view2 when you open the filter widget in view1, it should and will be automatically updated in sync - otherwise, it is a bug (the time when you saw a full list probably was caused by a slow network or loading process).
In ExB, filters on the default data view affect all widgets that use the data or its views. Filters on a specific data view only affect widgets that use the same data view. You can refer to the detailed doc on ExB > Select data.
If you do not want these two Section views to have filters affecting each other, try creating separate Data views for each and then choose the correct data view for filtering - this is the expected way to achieve similar cases:
@TheGamer It seems like the configuration of the Clause set has some logical defects.
In view2, the configuration contains two single clauses; while in view1, it is two clauses within one clause set:
Currently, you could change Filter1's setting to two single clauses, like that of Filter2, as a workaround.
In the meantime, we'll try to fix the problem. Thanks for bringing it up.
