Dear community,
I am having trouble using more than one TableFilter tag in the Maps Config file to filter rows in a table. Using a single tag seems to work fine, but 2 or more returns no matches for the search/filter.
Please see examples below:
(works)
(does not work)
When using only the top or only the bottom filter in the (does not work) example, the filter seems to work properly. I'm wondering if this issue could be related to using view tables? Am I doing something wrong? Is there a workaround for this?
Any help is appreciated. Thanks!
This configuration looks correct. Did you also put filterVars="myFilter" on the TableSourceInfo tag? In the SLNet Client Test tool it's possible to verify the result of the filters, either by following the Maps connection, or by sending a GetPartialTableMessage with specifying the same filters (replace the [myFilter] with its value). I assume these parameter ID's are of the same (view) table? Or is this a FK (maybe a relation is missing)?
Hi Wim,
Thank you for your help! Yes I did include the filterVars="myFilter" on the TableSourceInfo tag. And yes, the PIDs all belong to the same view table.
I want to emphasize that using any single filter seems to work every time, but 2 or more cause the search to break. Could this be an issue with maps when applying multiple filters to a view table?
As this question has been inactive for a long time, we will now close it. If you still want further information, could you post a new question?