How to Make Quickbase Record Pickers Show the Right Records (Forms and Grid Reports)

Two questions keep coming up in the Quickbase community about record pickers, the dropdown you use to choose a parent record from a child record:

• In Record Picker in Grid Edit, a builder found that the picker in Grid Edit jumped by first letter instead of searching, and that the report-based picker they had set up on the form did not carry over to Grid Edit. The answer back in March 2025 was that you could not set a report for the picker in Grid Edit.
• In Default search fields in a table-to-table relationship in a form, someone wanted to change which fields show in the parent picker on a child form.

Both have better answers in 2026. Grid reports replaced legacy Grid Edit, and grid report columns can now have their own picker override. Report-based pickers on forms also show far more context than they used to. This guide covers all three places you can control a picker and how to set each one up.

The example we will use

To keep the steps concrete, picture two tables:

• Projects (parent): Project Name, Project Manager, City, Status.
• Tasks (child): each task has a Related Project reference field pointing at Projects.

Suppose there are two projects called "Website Refresh", one managed by Sarah Lee in Denver and one by Mike Chen in Austin, plus a few old projects marked Inactive. Users picking a project on a task need to tell the two Website Refresh projects apart, and they should not see inactive projects at all.

The three picker settings at a glance

The more specific setting wins. A form override only affects that form, and a grid report column override only affects that grid report. Everything else falls back to the default picker.

Answering the Grid Edit question (thread 15024)

The short version: legacy Grid Edit never had a picker report setting, and it is not getting one. What changed is that Grid Edit itself has been replaced.

• Grid reports became generally available on May 21, 2026 (release note). They replace legacy table reports and Grid Edit with a single spreadsheet-like report you can edit inline. New apps use them by default. Existing apps keep the legacy experience until you turn grid reports on.
• May 7, 2026: grid report columns gained a record picker override, Based on report (release note). The picker shows the filtered set of records from the report you choose, and that report's first three fields.
• July 16, 2026: a second option, Based on field, let you base the picker on a lookup field from the child table that points to the parent (release note).

All three are on Team, Business and Enterprise plans.

One thing to be clear about: I have not confirmed whether typing into the grid report picker searches as you type or still jumps by first letter. What the override does give you is a shorter, filtered list with the fields you choose, which makes the first-letter problem much smaller in practice. Test typing behavior in your own app.

Step 1: Turn on grid reports (existing apps only)

This switch is app-wide, so try it in a copy of the app or a quiet window first, and check any reports people rely on daily.

1. Open the app and go to App Settings.
2. Open App Properties, then Advanced Settings.
3. Set Use grid reports in this app to Yes and save.

If your app was created after grid reports launched, it is probably on already.

Step 2: Build the report the picker will use

Do this on the parent table (Projects in our example).

1. Create a new report on Projects. A plain table-style report is fine.
2. Put the columns you want people to see first. For Based on report, the picker uses the first three columns, so order matters: for example Project Name, Project Manager, City.
3. Add filters for what should be pickable, for example Status is not Inactive.
4. Sort it the way people think about the list, usually by Project Name.
5. Save it with a clear name such as "Picker - Active Projects" so nobody deletes or rearranges it later without knowing what depends on it.

Step 3: Set up a standalone grid report on the child table

Column properties are only available on standalone grid reports. They are not available on default reports, table home pages, or reports embedded on forms or dashboards. So if your users do their bulk editing from a table home page, give them a saved report instead.

1. On the Tasks table, create (or open) a saved grid report that includes the Related Project column. You can also use the reference proxy column, such as the project name shown on the task.
2. Save it with a name people will find, such as "Tasks - Quick Edit".

Step 4: Override the picker on the column

1. Open the Tasks grid report and click the More menu on the Related Project column header.
2. Choose Column properties.
3. Under Record picker, choose one of:
   • Based on report, then pick "Picker - Active Projects". The picker now lists only active projects, showing Project Name, Project Manager and City.
   • Based on field, then pick a lookup field on Tasks that comes from Projects (for example a Project Manager lookup). The picker then shows that field instead of the default view. Use this when one extra field is enough to tell records apart and you do not need to filter the list.
4. Save the report.

Step 5: Test it as a regular user

1. Open the grid report, click into a Related Project cell and open the picker.
2. Confirm inactive projects are gone (Based on report) and that the two Website Refresh projects are easy to tell apart.
3. Test with a user in a typical role, not only as an admin, so you see what they see.
4. Point people to this saved report for bulk edits instead of the table home page, since the override does not apply there.

Answering the child form question (thread 15364)

The question here was: on a child form, how do you change which fields show in the parent record picker? There are two levels, and most apps want both.

Option A: Change the default picker for every form

The default picker is controlled on the child table, not the parent. That catches many people out.

1. Open the child table (Tasks) and go to its table settings.
2. Open Advanced settings.
3. Find Identifying Records (the setting for which fields show in the record picker).
4. Choose up to three fields from the parent, for example Project Name, Project Manager and City.
5. Save.

Every picker on that relationship without its own override now shows those three fields. Quickbase's help article Setting record picker display fields walks through the same setting. This option does not filter anything: every parent record the user can see still appears.

Option B: Use a report-based picker on the form for more fields and a filtered list

On new forms, you can base the reference field's picker on a report from the parent table instead of the default. Since October 2, 2026, report-based pickers on forms show up to 9 fields per row instead of 3 (release note). This is on Team, Business and Enterprise plans.

1. On the parent table, build a report as in Step 2 above, but this time you can include up to nine columns, for example Project Name, Project Manager, City, Status, Start Date and Client Type. Keep the most useful columns first.
2. Add the filters that decide which parents can be picked, such as hiding inactive projects.
3. Open the child form (the Tasks form) in the new form builder and select the Related Project field.
4. In that field's settings, find the record picker options and switch the picker to use a report, then choose the report you just built. The exact wording can vary slightly between form versions, so look for the record picker setting on the field itself.
5. Save the form, open a task, and open the dropdown. Each row should show the report's columns, and only records that pass the report's filters should appear.

Two things to keep in mind:

• The report's filters decide what can be picked on that form. That is handy for hiding inactive records, but double-check you are not hiding records someone legitimately needs.
• This override belongs to that form. Other forms, and grid reports, keep using the default picker unless you set them up too.

Which one should you use?

• You want the same few fields everywhere: set Identifying Records on the child table (Option A). It is quick and covers every picker by default.
• People struggle to tell similar records apart on a form: use a report-based picker on the form (Option B) for up to nine fields.
• People pick from the wrong or outdated records: use a report-based picker, on the form or on the grid report column, so the report's filters hide them.
• The problem shows up during bulk editing: turn on grid reports, use a standalone grid report, and set the column's record picker to Based on report or Based on field.

A tidy setup for the example app is: Identifying Records set to Project Name, Project Manager and City; the Task form picker based on "Picker - Active Projects"; and the "Tasks - Quick Edit" grid report column using the same report. Users then see the same filtered list wherever they choose a project.

Common snags

• The override is missing from Column properties: make sure you are on a saved, standalone grid report and not the table home page, a default report or an embedded report, and that grid reports are turned on for the app.
• Only three fields show on the grid picker: that is expected for Based on report on grid reports. The nine-field view is for report-based pickers on forms.
• The picker shows the wrong fields on every form: check Identifying Records on the child table, not the parent.
• Someone rearranged the picker report: the picker follows the report's column order and filters, so treat that report as part of your app's setup and name it clearly.