October brought plenty of quiet Quickbase polish. Three Released items are worth a closer look for owners, ops leaders, and builders: clearer related-record picking on forms, file work inside grids, and Pipelines that no longer wipe mappings when you retarget a step. All three are generally available on Team, Business, and Enterprise. They are not betas or Upcoming announcements.
Related-record pickers: up to 9 fields (2026-10-02)
Report-based record pickers on forms can show up to nine fields per row instead of three. That matters when two projects share a name, or two customers look identical until you see city, site code, or account manager.
Illustrative: On a Service Request form, Dana used to guess between two “Acme” sites. With more picker columns—site code, address, region, status—she can choose the right parent without opening another tab.
Use a dedicated parent-table report for the picker, put the most distinctive fields first, and base the form’s reference field on that report. One limit to remember: the note covers report-based pickers on forms. Quickbase’s help for table Advanced settings → Identifying Records still documents up to three fields (page last updated May 2026). Don’t assume every picker path jumped to nine.
Files in grid reports (2026-10-28)
Official release note · Help: edit file attachments in grids
You can upload, replace, delete, restore, and lock file attachments in grid reports—standalone, on dashboards, or embedded on forms—without opening each record. Drag-and-drop works; undo/redo applies before save; locked files stay locked until unlocked.
Illustrative: Marcus filters Open Submittals, drops PDFs onto attachment cells, updates status, and saves in batches. When unsaved changes (files and text) near the save limit, Quickbase warns at about 80% and turns Save off if you go over. Each file can be up to 100 MB.
Turn this on where people already triage work: editable grid reports with the attachment column visible. Keep columns wide enough for the upload control when you can. Native attachments are still one file per field—this changes where you manage that file, not the one-file model. Required fields and role permissions still apply.
Pipelines keep field values on retarget (2026-10-22)
Official release note (postponed from 10-20) · Help: change a step’s account, app, or table
When you switch a step’s connected account, app, table, or object type, matching field values stay put. Values that don’t match the new target are saved (not deleted) and can reload when those fields return. Review them under Fields with saved values on the step or in the side panel—copy, reload, or discard.
Illustrative: Priya rotates a Quickbase channel step to a new service account. Status and Owner mappings remain; a field the new account can’t see lands in saved values for her to discard or restore later.
Treat every switch as a review, not a free pass. Failed switches leave the step unchanged. An account that can’t use the step’s fields requires an explicit clear. Discarding saved values is permanent; a step can hold up to 500 saved values; a saved value only reloads into an empty field. Reconnecting the same account after expired credentials does not retarget steps.
What to do first
- Grid files if ops lives in editable reports—enable on those reports and coach the save-limit habit.
- Nine-field pickers where mis-links are common—fix the picker report, don’t just hope names are unique.
- Pipeline preservation for anyone cloning apps or rotating accounts—add “review saved values” before activate.
October shipped more than these three. These are the Released changes with the clearest day-to-day payoff for how people enter data, attach proof, and keep automations intact.
Based on Quickbase's public release notes and help documentation; not sandbox-tested.