Return to a Specific Step of a Multi-Step Quickbase Form After Adding a Child Record

A multi-step parent form is a great place to add child records — until the child save dumps you back on step 1. That is the problem in this community thread: someone is on step 3 of a new form, they add a child, and after the child saves they want step 3 again, not the start of the form.

On new forms you can fix that. Skip the native Add child button's return behavior and open the child yourself with a Formula - URL button that puts page=3 (or whatever step you need) into the return URL.

Why the native button lands on step 1

The Add child control that comes from a relationship usually returns with Rurl(). That function rebuilds "where you came from," but on a multi-step new form it often forgets which step you were on. The parent opens again in edit mode on step 1, and whoever was mid-form has to click back to step 3 before they can keep working.

Building the return URL yourself avoids that. Quickbase's z= parameter is the return destination after the add (or edit) form saves. If that destination already includes page=N, the multi-step form opens on that step.

This pattern is for new forms. Legacy multi-page / tabbed forms do not honor page=N the same way, and Quickbase is not investing in that older behavior. If you are still on a legacy form, convert the parent to a new form first, then use the steps below.

What you will build

1. Turn on Auto save when redirected away from the page on the parent table.
2. Add a Formula - URL button on the parent that:
   • opens the child add form with the related parent already filled in
   • sets z= to the parent edit URL with &page=3 (your real step number)
3. Put that button on step 3 of the parent form (and hide or ignore the native Add child control for that workflow).

After a child save, Quickbase follows z= and opens the parent in edit mode on that step.

Step 1: Turn on auto save on the parent table

The button will leave the parent form to open the child. If the parent has unsaved edits, you want Quickbase to save them first instead of showing a "Leave site?" prompt.

1. Open the parent table's settings.
2. Open Advanced settings.
3. Check Auto save when redirected away from the page.
4. Save.

This setting is per table. Put it on the parent table where the Formula - URL button lives. On many newer apps the box is already checked.

Step 2: Find the child table alias and the reference field ID

You need two values for the formula:

• The child table alias, something like [_DBID_LINE_ITEMS]. Open the child table → Settings → Advanced settings and copy the table alias shown there. If the table is named "Line Items," the alias is usually [_DBID_LINE_ITEMS]. Spaces and punctuation in the table name get turned into underscores.
• The reference field ID on the child that points at the parent (often labeled "Related Parent" or similar). Open that field's properties and note the field ID, like 7 or 19. In the URL it becomes _fid_7 or _fid_19.

Keep those two values handy for the next step.

Step 3: Add the Formula - URL button on the parent

1. On the parent table, add a new field.
2. Name it something clear, like Add line item.
3. Choose the Formula - URL type.
4. Paste a formula like this (swap in your values):

If(
  [Record ID#] > 0,
  URLRoot() & "db/" & [_DBID_CHILD_TABLE]
    & "?a=API_GenAddRecordForm"
    & "&_fid_XX=" & [Record ID#]
    & "&z=" & URLEncode(
         URLRoot() & "db/" & Dbid()
           & "?a=er&rid=" & [Record ID#]
           & "&page=3"
       ),
  ""
)

5. Check Display as a button and pick a button color if you like.
6. Leave Open Target in New Window unchecked so the child opens in the same tab and z= can bring people back cleanly.
7. Save the field.

What each piece does

Replace [_DBID_CHILD_TABLE] with your real alias, _fid_XX with your real reference field ID, and 3 with your real step number. Step numbers are 1-based and match the order of steps in the new form builder.

The If([Record ID#] > 0, ..., "") wrapper hides the button on a brand-new parent that has not been saved yet. There is no Record ID# to pass to the child or to put in the return URL until that first save.

Example with concrete names

Say the parent is Work Orders, the child is Line Items, the child's Related Work Order field is FID 7, and the line-items step is step 3:

If(
  [Record ID#] > 0,
  URLRoot() & "db/" & [_DBID_LINE_ITEMS]
    & "?a=API_GenAddRecordForm"
    & "&_fid_7=" & [Record ID#]
    & "&z=" & URLEncode(
         URLRoot() & "db/" & Dbid()
           & "?a=er&rid=" & [Record ID#]
           & "&page=3"
       ),
  ""
)

On work order 42, after URL encoding, the return destination inside z= looks like:

https://yourrealm.quickbase.com/db/PARENT_DBID?a=er&rid=42&page=3

Step 4: Put the button on the right step of the form

1. Open the parent new form.
2. Go to the step where people add children (step 3 in the example).
3. Add the Add line item Formula - URL field there.
4. Save the form.

If the native relationship Add child control is also on that step, remove it or leave it off the form for this workflow so people only use the button that returns to the correct step.

Step 5: Test the round trip

1. Open an existing parent record in edit mode.
2. Go to step 3.
3. Click Add line item.
4. Confirm the child add form shows the related parent already filled in.
5. Enter a couple of fields (for example Line description = "Filter replacement" for Sarah Lee's work order) and save.
6. Confirm you land back on the parent in edit mode on step 3, not step 1.

If you land on the right record but the wrong step, double-check the number after page=. If you land somewhere else entirely, check that z= is wrapped in URLEncode(...) and that the return URL uses a=er with the parent Record ID#.

Optional: non-default parent form

If the parent uses a specific form that is not the table default, add &dfid=FORMID next to a=er in the return URL:

&z=" & URLEncode(
   URLRoot() & "db/" & Dbid()
     & "?a=er&dfid=10&rid=" & [Record ID#]
     & "&page=3"
 )

Find the form ID on the table's Forms page. Without dfid, Quickbase uses the default edit form for the user's role, which may not be the multi-step form you built.

Returning to different steps from different buttons

Nothing says every button has to come back to the same step. You can add two Formula - URL fields — one that returns with page=3 and another with page=5 — and put each on the matching step of the form. Hard-code the step number in each formula; that is clearer than trying to read the current step dynamically.

Checklist

• Parent table has Auto save when redirected away from the page turned on
• Parent form is a new form with steps (not a legacy multi-page form)
• Formula - URL button (not rich text) opens in the same tab
• Child alias and _fid_XX match the child table and reference field
• Return URL uses a=er, the parent [Record ID#], and &page=N
• z= value is wrapped in URLEncode(...)
• Optional &dfid=FORMID if the multi-step form is not the default
• Button sits on the step where people add children; native Add child is not fighting it

Once that is in place, adding a child from step 3 and landing back on step 3 becomes the normal path instead of a surprise trip to the start of the form.