Currently creating a layout that contains a filter by attribute section, a map, and an associated table. The filter by attribute section currently has four queries dealing with different fields we would like to perform on the data. So, it needs to have four distinct types of triggers added when selecting the feature in the map and the table based off the differing fields.
What I have discovered is that each of the four queries do not seem to be independent when you add additional triggers. It appears that if you have a trigger for Field 1, a trigger for Field 2, a trigger for Field 3, and a trigger for Field 4 they are all part of the same filter by attribute and it will use all 4 (Instead of the individual trigger you want specifically for the field you are currently filtering).
Does this mean even though I am using the same table for all four queries, I will need to add them each separately as their own filter by attribute widget? Allowing them to have individual triggers that will not flow directly from one query to the other when I keep the four queries together in the same filter by attribute widget?
