Resource Icons
![](https://i.imgur.com/Otf8WJF.png")
Latest Highlights
Check Out The Latest in The Qrew
3 MIN READ
The Quickbase Extensions Package just got even better.
At Empower, we introduced three new Extensions that are now included in the package at no additional cost. That means every customer with the...
19 hours ago
Quickbase trainer (and occasional Bob Ross impersonator) RobHenderson shows us one way to approach complex app relationships.
Want to explo...
28 days ago
At Empower, we announced that grid reports are generally available in Quickbase. Grid reports bring that familiar, spreadsheet-like experience into Quickbase, so users can work with operational data ...
1 month agoThe Content Feed
Feed
URL Add Related Form (But popup like embedded Reports)
I am trying to make a URL Button to add a child record in a form Example: URLRoot() & "db/" & DBID & "?a=API_GenAddRecordForm&_fid_13=" & ToText([Record ID#])& "&dfid=10&popup=1" I also tried: URLRoot() & "db/" & DBID & "?a=API_GenAddRecordForm&_fid_13=" & [Record ID#] & "&target=popup&popupwidth=500&popupheight=400" I also tried these checking In Same Page, In New Window, And In Pop Up.but the button does not pop up like the embedded report. is it possible to make a button that works this way on PC and Mobile as it does in the Report button Link?July Qrew Events
July Qrew update! We’ve got a lighter meetup month with no virtual Qrew meetups scheduled in July, but a few regional Qrews are keeping the momentum going. Here’s what’s on the radar for July 2026: Boston Qrew (In-person or Virtual): July 22, 4:30–6:30 pm ET. Register here Portland Qrew (In-person or Virtual): July 22, 3:00–4:30 m PT. Reach out for details here Atlanta Qrew (Virtual): July 23, 4:00–5:00 pm ET Register and join here Philly Qrew: No Qrew meetup in July Denver and Dallas: TBD Just a reminder that anyone can join any virtual Qrew meetups in any of the regions to meet network, hear use cases, and share challenges and wins. Thanks and hope you’ll be able to join!Better Workflows, Built In
The Quickbase Extensions Package just got even better. At Empower, we introduced three new Extensions that are now included in the package at no additional cost. That means every customer with the Extensions Package or 30-day free trial now has access to nine tools designed to help you build more complete workflows without leaving Quickbase. Whether you're creating documents, collecting signatures, sending notifications, or mapping work in the field, Extensions help keep every step connected. And with these latest additions, it's even easier to automate document-heavy processes that often slow teams down. A Quick Refresher on the Extensions Package The Extensions Package brings together tools that help you manage work from start to finish inside Quickbase. Instead of piecing together multiple applications, you can create documents, collect signatures, communicate with customers, and visualize work in one connected workflow. The original package of six tools includes: Exact Forms Plus: Create Word and PDF documents directly from your Quickbase data with a single click. XL Docs: Generate formatted Excel files that are ready to share or analyze. JuicedSign: Send, sign, and track legally binding e-signatures without leaving your workflow. Text My Quickbase: Send and receive text messages tied directly to your Quickbase data. Courier: Send emails, reminders, and notifications from inside your workflow. QB Maps: View your data on live Google Maps to see locations, routes, and activity in real time. Now, these are joined by three new Extensions that make document workflows even more efficient. Meet the Three New Extensions Many business processes still depend on documents. Quotes, permits, inspection reports, contracts, invoices, and customer packets all need to be created, combined, reviewed, and shared. The newest Extensions help you automate those steps, so your team spends less time moving files around and more time moving work forward. PDF Stamper Many organizations rely on standardized PDF forms that can't be edited, but still need personalized information. PDF Stamper lets you place Quickbase data exactly where it belongs on any fixed-format PDF, including certificates, brochures, applications, and other standard forms. Your documents stay consistent, your data stays current, and there's no manual editing before you send them. PDF Merger Project documents rarely live in one place. Supporting files often come from multiple records, tables, and formats. PDF Merger brings them together automatically. Combine Word documents, Excel spreadsheets, images, PDFs, and other supported files into a single PDF that's saved back to Quickbase. Instead of downloading, combining, and uploading files by hand, you can complete the process in one step. Package Builder Some workflows require several documents before they're ready for review or approval. Package Builder helps you prepare everything at once. Run multiple document generation Extensions from a single record, combine the results into one complete package, and route it to the next step in your process. Fewer manual steps mean faster reviews, quicker approvals, and more Explore What's New If you already have the Extensions Package, these new capabilities are available to use now. If you're exploring Extensions for the first time, the 30-day free trial now includes all nine tools. Ready to take a closer look? Start with these resources: Learn more about the Extensions Package Watch our recent webinar on the newest Extensions Explore each of the 3 new Extensions: PDF Stamper PDF Merger Package Builder Start your free Extensions trial Join Extensions Office Hours Every workflow has small tasks that add up over time. The newest Extensions help remove more of that manual work, so your team can spend less time managing documents and more time keeping work moving. We can't wait to see what you build next.How to add Tabs (Pages) to only a specific section of a form?
Hi everyone, I’m trying to organize a form using Tabs (Pages), but I’m running into some confusion with how Quickbase handles them.Previously, I was able to add new sections below existing ones without issues. However, when I try to add a new Page (Tab), Quickbase automatically moves all my existing fields into Page 1 and puts the new fields on Page 2. The tabs also always appear at the very top of the form. What I actually want is to have tabs (or a tab-like experience) applied to only a specific section lower down in the form, without wrapping the entire form into multiple pages. Is there a way to achieve this? Or what is the recommended approach — using multiple Pages, Sections with rules, or a completely different method? Any advice or best practices would be greatly appreciated! Thanks in advance.Improving pipeline resilience: field rename handling and stable step identification in Pipelines
Quickbase applications and workflows evolve, fields get renamed and pipelines get reorganized. These are routine activities — but until now, both could affect the accuracy of a pipeline configuration in ways that were not always immediately visible, requiring manual intervention to identify and correct. Two recent updates to Quickbase Pipelines address this directly: field renames in Quickbase are now automatically detected and applied, and step identifiers are now permanently stable regardless of how a pipeline is reorganized. This post describes each change, the mechanism behind it, and the practical implications for pipeline reliability and troubleshooting. Background As pipelines grow in complexity, it becomes common to reference the output of one step in the logic of another — passing a value forward, applying a transformation, or building conditional logic around a result. These references are written as Jinja expressions, and they depend on two things staying consistent: the name of the field being referenced, and the identifier of the step whose output is being used. Both of these could previously change as a result of ordinary activity — renaming a field in Quickbase, or reorganizing steps in the pipeline designer — without any corresponding update to the expressions that depended on them. When a field was renamed in Quickbase, Pipelines had no mechanism to detect the change. Any step mapping or Jinja expression using the previous field name would continue to reference a name that no longer existed, producing incorrect output or failing without a clear indication of the cause. When steps were reordered, a similar problem occurred at the pipeline level. Step identifiers were alphabetical and positional — reassigned to maintain sequential order whenever the pipeline was reorganized. An expression that correctly referenced a step before a reorganization could, afterward, point to an entirely different step or resolve to nothing at all. In both cases, the expressions appeared intact in the designer while no longer functioning as intended. Stable field references: automatic rename handling When a field is renamed in Quickbase, Pipelines detects the change at the next refresh and applies two updates together: Step mappings — any step that mapped a value to the renamed field continues to do so under the new name, with the configured value preserved. Jinja template references — standard {{ refID.field_name }} expressions referencing the renamed field, across every step in the pipeline, are rewritten to use the new name. When the update takes effect The update is applied the next time Pipelines re-reads a step's fields from Quickbase. This occurs in three situations: Refresh Schemas — re-reads all steps in the pipeline simultaneously. Recommended after multiple field changes in Quickbase, or to confirm the final state of a pipeline following rename activity. Single step refresh — re-reads only the selected step. If a rename is detected, Jinja references to that field are updated across all steps in the pipeline, not just the one being refreshed. Certain step edits — adding or changing a field via the field selector, or modifying a step's options, triggers an automatic schema re-read as part of saving. Any rename present at that point is applied as part of the same operation. Pipelines continue to execute correctly between a rename and the subsequent refresh — the old field name remains valid until a refresh occurs. No configuration is lost in the interim. Scope Automatic rename detection applies to standard Jinja field references ({{ redID.field_name }}) and step mappings. References embedded in custom Jinja expressions — logic or transformations written manually — are not automatically updated and should be reviewed and corrected manually after a rename. This behavior applies to Quickbase fields only; field renames in other connected channels may still require manual reconfiguration. Stable step references: Reference ID and Step Number Step identification now separates into two distinct identifiers, each with a defined and exclusive purpose. Reference ID (Ref ID) is a permanent identifier assigned to a step at creation. It is not modified by reordering, insertion, or deletion of surrounding steps, and is never reassigned after a step is removed. The Ref ID is the identifier to use in Jinja expressions, and the one that appears in activity logs, error notifications, and field usage views. Ref IDs use an extended alphabetic format: aa, ab, ac… zz. Step Number is a sequential position indicator (1, 2, 3…) that reflects the step's current place in the pipeline. It updates automatically when steps are reordered and is intended for visual navigation in the designer and for following execution order in activity logs. Step Numbers should not be used in Jinja expressions. Reference ID Step Number Format aa, ab, ac… 1, 2, 3… Changes on reorder No Yes Use in Jinja Yes No Primary purpose Expressions, logs, field usage Navigation, execution order Step outputs should be referenced in Jinja using the Ref ID: {{ aa.field_name }} Because the Ref ID is permanent, this expression remains valid after any restructuring of the pipeline — reordering steps, inserting new steps, building parallel branches. The reference is unaffected by positional changes. Troubleshooting with stable identifiers Activity logs now include both identifiers. When reviewing a failed run, it is possible to determine unambiguously which step is referenced — because Ref IDs are permanent and never reassigned, the step in the log is definitively the same step in the designer, regardless of any reorganization that occurred in between. The Quick Reference widget provides a consolidated view of every step's Ref ID and Step Number, searchable by step name, number, or ID, with direct navigation to any step in the designer. The path from an error in a log entry to the relevant step in the designer is a single action. Backward compatibility Existing pipelines require no changes. Single-letter identifiers from pipelines created before this update (a, b, c…) are now treated as Ref IDs — permanent, stable, and functionally equivalent to the new extended format. New steps added to those pipelines receive extended-format Ref IDs (aa, ab…). Pipelines containing a mix of both formats are fully supported across duplication, export, and import. Implications for pipeline reliability and maintenance Together, these updates stabilize both components of a Jinja expression: the step identifier and the field reference. An expression such as {{ aa.customer_manager }} will resolve correctly regardless of subsequent pipeline reorganization or field renames in Quickbase. More broadly, the changes reduce the conditions under which routine application maintenance can introduce silent failures in pipeline behavior. Field renames are reflected automatically at the next refresh rather than discovered following a failed run. Step references in activity logs are unambiguous and consistent over time, independent of the pipeline's current structure. The information available during troubleshooting — log entries, step identifiers, field usage — is more reliable and more directly actionable. Read more in our help documentation about step identifiers and field renames.
