Skip to main content
Question

Quickbase Pipelines: Cannot Populate Required Reference Field from Search Records

  • May 8, 2026
  • 0 replies
  • 69 views

Forum|alt.badge.img

I am working on a app that serves as an intake staging area for a public facing form. The forms only identifiers to the customer is an account number. I am tying to use this account number to copy the record to a different application using that number as reference to attach to a table with existing records. My pipeline is currently setup in the following way:

Step 1:
Intake record which triggers on a status change from "pending" to "approved" We will call the app this step looks at "Intake"

No issues with this step

Step 2: 
Search records from what we will call the "Live" app which has an "Organizations" table with entries including the org name, details and the EIN#. Fields for subsequent steps here include that account #. 

Step is finding the EIN# and shows the org name in the output.

Step 3:

Basic condition to only proceed if records are found matching account #.

Step 4:

Creates a new record in the Live app primary table. Organization is a require field and I have  {{b[0].id}}} as the entry.

Issue: Once the record is created it is showing the EIN# itself in the organization field, not the org name. It is not properly going through the relationship to pull the relevant organization information.

Forum|alt.badge.img+11
  • Registered
  • May 8, 2026

It sounds like you are populating the organization field with the "Related ..." or foreign key. Rather, you would want to have a look up field for the organization name, and then populate that in the organization field. Depending on your structure, you may create a field specifically for this purpose like a formula which gets/displays organization name and use that as the source for your new record's organization field.


RoyWanyoike
Forum|alt.badge.img+13
  • Registered
  • May 12, 2026

Make sure the field you are mapping to is a true Reference field (not a Text or Formula field). Also if the output you're expecting is one record you can use the first step as a lookup and use either EIN# or account number and hence in the create step you won't need to do indexing like it will just be {{b.id}} (no [0] needed).


Forum|alt.badge.img
  • Registered
  • May 13, 2026

Best practice is to always pass-down the RID to the child table.  (Even if you have a different key field, pass it and the RID down).  Then you can use it for filling Related Reference fields.