# Filtering table from multiselection dropdown **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [June 14, 2024, 10:45am UTC](https://forum.inductiveautomation.com/t/filtering-table-from-multiselection-dropdown/91859 "2024-06-14T10:45:57Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [June 14, 2024, 11:11am UTC](https://forum.inductiveautomation.com/t/filtering-table-from-multiselection-dropdown/91859/2 "2024-06-14T11:11:07Z")
(For anyone else, this is a follow up to [Checkbox filter, selected box and non selected boxes - #9 by Transistor](https://forum.inductiveautomation.com/t/checkbox-filter-selected-box-and-non-selected-boxes/91754/9)) Here are two ways: First, create a custom property `custom.tableFilter` on the view and make a bidirectional binding to it from the dropdown `props.value`. (This avoids all the getParent / getSibling syntax and will make your script less "brittle".) 1: Use the custom property as a parameter in the SQL query. This will automatically refresh the binding if the dropdown selection changes. 2: Use the custom property to trigger a script transform on the SQL results. Here's how I would do that: - On the Table component add a custom property, `custom.data`. Create a query binding on that so that it retrieves all the records. - On `props.data` create a property binding to `view.custom.tableFilter`. (Now when the dropdown selection changes this binding will refresh.) - Add a Script Transform to script the filter. The data will be available from `self.custom.data` and the filter will be passed as `value` into the script. Have fun. --- _[View the full topic](https://forum.inductiveautomation.com/t/filtering-table-from-multiselection-dropdown/91859)._