If you’ve ever been scanning your data, noticed something that needs a quick fix, and felt thrown off when you had to shift into a completely different interface to make the change, you are not alone.
That switch costs you context. You lose your place, break your flow, and have to reorient in a new UI just to make a small change, then come back and find where you left off.
Grid reports are designed to directly address this problem by providing one, unified way to view and update data directly in line without breaking your flow. They also feature many more spreadsheet-like interactions that will feel familiar to users coming from a background in Excel.
Since launching to Open beta in October, we’ve been focused on two things:
- Listening closely to what’s working (and what isn’t)
- Shipping a steady stream of feature enhancements and bug fixes
Here’s where things stand today - what we’re learning, what we’ve improved since launch, and what’s coming next.
What we’ve learned since October launch
Since launching Open beta for Grid Reports in October, we’ve seen steady real-world usage - over 50,000 users have tried Grid Reports so far. That scale of use has been invaluable, because it turns assumptions into concrete learnings about what matters most in the report experience.
Here are a few themes we’ve consistently heard - and how they’re shaping what we deliver:
- Don’t pull me out of my workflow.
Users want to stay in the report to make quick updates without losing context. That’s pushed us to focus on in-place editing behaviors that feel seamless, not disruptive. - Give builders control and confidence.
Teams need flexibility and guardrails. Builder/admin controls are critical for adopting Grid Reports in the right places, at the right pace. - Spreadsheet-like is about the details.
It’s not just about editing in a grid - it’s about the little things that make the experience feel intuitive and efficient (how headers display, how links behave in edit mode, how resizing works, and more). - Embedded use cases matter just as much as standalone reports.
Many workflows happen inside forms and dashboards, so parity and reliability in embedded contexts are a major priority. - Trust comes from quality.
The more users rely on Grid reports for productive work, the more important stability becomes. That’s why a big portion of our progress since October has been focused on bug fixes and quality.
Based on these learnings, here’s what we’ve improved so far and what we’re tackling next.
The improvements so far
-
Default report option to configure inline editing availability
What changed:
Added a new option in each table’s default report setting to control whether inline editing is available in grid reports.
Why it matters:
Allows builders to control, table by table, if inline editing is available by default.
Since we're making it easier than ever to edit data, we want to make sure builders have the controls they need where they need them to decide where editing should be available. Once a default is configured, builders can choose to inherit the default setting or override it for each report. -
Column Header Wrapping
What changed:
You can now choose whether column headers wrap onto multiple lines or truncate to one line, which is especially helpful for wide reports or fields with longer names. Builders can configure the default behavior in report settings. End users can set their own preferences that we’ll remember each time they visit the report.Why it matters:
Better readability. -
Interact with links in edit mode
What changed: You can now click links and buttons while making inline edits in grid reports - both in standalone reports and embedded reports on forms.
Why it matters: Link/button interactions now behave as users expect, so you can keep working without having to stop editing just to navigate or take an action.
-
Create child records before the parent has been saved
What changed:
When you’re creating a new parent record that includes an embedded child report, you can now add one or more child records immediately - before the parent record has been saved. And they will all be created and associated upon save.Why it matters:
This removes a common workflow break - previously you had to save the parent first, then re-open the record (or wait for a reload) to start adding related items. Now you can capture everything in one pass - fewer clicks, less context switching, and less risk of missing details.This unlocks critical workflows many of you have highlighted, such as:
- Projects → Tasks (create the project and immediately build the task list)
- Orders / Requests → Line items (enter multiple items while you’re still in the intake flow)
- Cases / Incidents → Follow-ups or Action items (log the issue and the next steps together)
-
Many other small-but-mighty delighters
- Added builder control over the availability of the 'Add row' button in embedded reports
- The 'Full report' button for embedded reports is now accessible in edit mode as well
- Provided Open in new tab option via right click in multiple scenarios for standalone and embedded reports (including for builders in forms!)
- Non-editable field tooltips that appear only on click (less noise, more clarity)
- Updated filters for text and user field types, matching common search expectations
-
Quality & reliability work (the part you don’t always see)
Alongside feature improvements, the we have been investing heavily in stability:
- 200+ bugs addressed since October
- Continued work on known issues and UX refinements as part of the path to GA
What’s next / Coming soon
We’re keeping the momentum going, and the next set of work is focused on making Grid Reports more consistent across environments, more inclusive and even more polished and reliable at scale.
- New column properties
We’re continuing to expand column properties, allowing builders to mark fields required at the report level and override record pickers (similar to forms)
- Content overflow enhancements
We’re providing a more intuitive way for users to interact with data that extends past the edge of a cell without adjusting row height
- Improved keyboard navigation & accessibility
We’re actively working on improving keyboard navigation & shortcuts and support for screen readers
- Cross-browser support
We’re focused on making Grid Reports fully functional across all Quickbase-supported browsers.
- Continued big push on quality
We continue resolving high impact issues and bugs
- Even more user delighters, such as:
- Make undo/redo work for deletes as well
- Improve support for environments like iframes displaying Grid Reports
- Enhance copy/paste between reports
Learn more about our latest enhancements as well as upcoming features in our Release notes app.
Path to GA (general access) and what this means for existing apps
As we continue toward General Availability, we’re aiming to minimize disruption and maximize flexibility for customers.
- When Grid Reports become Generally Available, we’re not planning to change the default table report experience for existing apps. If you aren’t using them already, it is up to you when you are ready to do so.
- Grid Reports are already defaulted on for new apps (for all customers)
- Legacy table report experiences will remain available, but will move into limited support over time (meaning you can keep using them, but we won’t be investing in enhancements there going forward)
We’re aligning the GA timing with Empower in May 19–20.
There will be more information coming on that front in the next months!
We’d love to hear from you!
If you’re already using Grid Reports - thank you! Your feedback is directly shaping what we build next.
If you haven’t tried them yet, Open Beta is a great time to test in real workflows and tell us:
- Where inline editing saves you the most time
- What still needs improvement
- Any “paper cuts” that break your flow (especially in embedded reports, dashboards, and high-usage tables)
You can submit your feedback, feature requests or report bugs you’ve found, directly from your app, by hitting the Help on the top right and using the respective buttons.
Please keep the feedback coming.
We’re building this with you!
