I have a table (product list) that contains a matrix of boolean features. I have a user table that also has the same boolean features that are added to the collection allowing the user to enable/disable them. I want all items to show initially and reduce the list as user required features are checked. The problem I am having is with each non-true filter condition is limiting the list, whereas I only want true conditions to limit the list.
1 Like
Can you provide screenshots of your table, screens, filter configurations, and anything else that might be relevant? I’m having trouble visualizing what you are explaining.
1 Like
Are you planning for those features to work as filters, so users only see products that match the options they’ve selected?
2 Likes
Thank you both. I did set up if then else to change the checkboxes to a label that indicates the feature desired and then created a joined field of all features for each device, and then filtered the list based on each slider (feature label) found within the device features field.
Still not fulling picturing your setup but I imagine you have a bunch of boolean columns followed by a bunch of IF columns and a bunch of checkbox screen components. I feel like your setup could be vastly simplified with a single choice component to select features (for both the user and the product), a Split Text column to convert the comma separated list into an array, and a Relation or Query column to get the matching records you want. Much easier than creating several boolean and IF columns. Plus, adding a feature is as simple as adding a row to a table that feeds the choice component (No need to add additional columns and screen components. Just add a record to a table and you are done.)
Jeff, I turn the grid into features, which then are joined into a single cell to use with ‘contains’. The results look good so far. PS: I am having difficulty opening a form with a lookup button that shows a searchable list of values, and getting certain fields from the tapped row to push back to the original form fields. The lookup all works, but the table’s Set Column Values are not pushing values, and the Close Overlay action does seem to be firing
Yeah, that could be consolidated into a single Text column to hold all feature selections from a single choice component as a comma delimited list, followed by a single Split Text column to convert the comma delimited list into an array. One component and two columns. Much easier set up and you aren’t forced to jump into the builder each time you want to allow additional features. It’s a lot more dynamic and future proof.
1 Like
I am unable to perform a simple button triggered lookup to a secondary table and push a selected row cell(s) back to the calling form. Set column value only shows the lookup table fields and not those of the calling form table. I’ve found nothing in documentation to help solve this either. This has to be a simple task to setup.