Limit Multi-select picks to one in linked table

Question

I have a table with employees and their details, including a multi select for their function(s).

In another table I have a roster where each person can be assigned a roster shift. As some employees have multiple functions assigned to them, I want to be able to specify when they are put on a shift what function they are doing (out of the ones previously assigned to that employee from the multi-select in the employee table).

At this stage if they have multiple functions selected in the employee table they all show in the roster shift record.

Thanks in advance
Harry

quickbasejunkie · Answer

There is no native capability to conditionally filter a multi-select type field. You could do this if the functions were child records.

The only other option would be to add the same multi-select field to the roster allowing you to specify which functions are needed for that shift. Then set up a way to 'check' the functions on the roster against the employee's functions and prevent the record from being saved if there is a mismatch.

meredithmoore5 · Answer

I keep reading that there is no 'native' capability to filter a multi-select field, so what is the non-native option. Is there one? I'm ready to go rogue.&nbsp;

quickbasecoachd · Answer

@QuickBase GirlCan you describe you use case.

meredithmoore5 · Answer

Pretty simple.&nbsp;I have Lot #'s (a lot of them). I have hundreds of inventory items (flavor powders) and each one of the flavor powders have many lot numbers.&nbsp;Example: Ingredient Inventory of Sherbet Flavor Powder of 60kg. That inventory may have 3 Lot #'s - (12kg) #123(30kg) #456(18kg) #789If I choose Sherbet Flavor Powder in my ingredient list (for a recipe), and I need 35kg, I will be using 2 lot numbers.I would like only the Sherbet Flavor Powder Lot #'s show in the multi-select.&nbsp;

alexcertificati · Answer

Curious to hear what the pros recommend for this one. My first thought would be, as I think QB Junkie alluded to above, that you'd rather be operating with the lot #s in their own table than as a multi-select field on the ingredients table. Assuming I'm understanding your setup correctly. That way when you go to pick a lot number for a recipe, rather than using a multi select of a million potentially unrelated lot numbers, you use a record picker to the lot number table that's filtered by related ingredient.

If your ingredient/lot number relationship is many to many (ie. a lot number can be associated up to more than one ingredient, as opposed to lot numbers being strictly child records to the records on the ingredients table), it gets a little stickier, but I think you'd still start with a lot number table, do the standard many-to-many technique to a joined ingredient/lot number table and then work from there.

Forum Discussion

Limit Multi-select picks to one in linked table

Related Content

Multi-Select Fields with Commas in Pipelines

If Then Else formula with a multi select field.

Calculation/Performance Limits Inquiry

Checkbox Fields Vs Multi-Select Fields for Tracking

Secure Links for Instant Access and Full Control