We can enable "searchable" to use search and filter for that column.
But there are still some limitations.
Let's say we have 2 tables: Orders (Parent) and Products (Children). They are referenced in 2 ways: via Ref and via Enum Type Ref.
Orders
ID
(Key) | Order
(Label) | Name
| Related Products
(REF_ROWS) | Related Products
(EnumList Type Ref) |
| Ord00001 | First order | William | Pro00001 , Pro00002 | Pro00001 , Pro00002 |
Products
ID
(Key) | Order
(Ref) | Order
(Enum Type Ref) | Product
(Label) |
| Pro00001 | Ord00001 | Ord00001 | Apple |
| Pro00002 | Ord00001 | Ord00001 | Banana |
Search and Filter
| | Example | Search (Ref) | Filter (Ref) | Search (Enum Type Ref) | Filter (Enum Type Ref) |
| In Products Table search for the Order's ID | Ord00001 | โ๏ธWorking | โ๏ธWorking (search box) | โ๏ธWorking | โ๏ธWorking (search box) |
| In Products Table search for the Order's Label | First order | โ๏ธWorking | โ๏ธWorking (search box and dropdown) | โNot working | โ๏ธWorking (search box and dropdown) |
| In Products Table search for the Order's Name | William | โNot working | โNot working | โNot working | โNot working |
| | | | | | |
| In Orders Table search for Product's ID | Pro00001 | โ๏ธWorking | โNot working | โ๏ธWorking | โ๏ธWorking (search box) |
| In Orders Table search for Product's Labels | Apple | โNot working | โNot working | โNot working | โ๏ธWorking (search box and dropdown) |
At the moment the only way I see to workaround the limitations is to add Virtual Columns that calculate the desired searchable values.
LinkedIn
Twitter
