Solving Filtered Multi-Selects in Quickbase

One limitation I run into fairly often in Quickbase is filtered multi-selects. Quickbase supports conditional dropdowns on relationship fields, which works well when a user is selecting a single option. The issue comes up when users need to select multiple options and still have those options filtered based on one or more previous selections.

Since multi-select fields can’t be filtered, users end up seeing options that don’t apply. I recently built a solution for this and wanted to share the pattern, since it’s reusable across a lot of different scenarios.

The Challenge

Out of the box:

• Conditional dropdowns only support single selection
• Multi-select fields can’t be filtered
• Users end up seeing options that don’t apply

In this case, the requirements were:

• Users must be able to select multiple options in both steps
• Only valid options should ever be shown
• The experience should feel simple and intuitive, not like a workaround

The goal wasn’t to force something into a multi-select field — it was to keep the user experience clean while still enforcing valid selections.

The Idea (High Level)

The approach was to:

• Break the selection into two steps
• Let Quickbase build the valid options for the user (for example, using a pipeline)
• Let users select from only those valid options

Rather than asking users to figure out what applies, the system does the work for them.

Example Use Case

Here’s a scenario people can apply this to:

• Step 1: User selects one or more Vendors
• Step 2: User selects applicable Services

The key requirement:

• Not all Services apply to all Vendors
• Users should never see invalid combinations

Instead of showing every Service and relying on users to know what applies, Quickbase only presents options that are valid based on what they selected in the first step.

User Experience

From the user's perpective:

1. The user selects one or more Vendors
2. The user saves/submits their changes
3. The system generates a clean list of only the valid Services

4. The user checks the Services they want

This ends up feeling very similar to a filtered multi-select, without exposing irrelevant options to the user.

Why This Works Well

This pattern:

• Prevents incorrect selections
• Keeps the interface clean and focused
• Is easy for users to understand
• Scales well as options grow
• Works for both many-to-many and one-to-many scenarios

How Others Can Reuse This

This approach works anytime:

• Selection B depends on Selection A
• Users need to choose multiple options
• You want to hide anything that doesn’t apply

What you'll need:

• A clear source of truth for valid combinations
• A step where the system generates valid options
• A simple selection step for the user

You don’t need the exact same data model - just the same concept. Replace “Vendors” and “Services” with whatever fits your use case.

April Barragan | Solutions Consultant

Website | LinkedIn | Knowledge Base