How Pipelines handles Quickbase field renames

When you rename a field in a Quickbase table, Pipelines automatically updates every pipeline that references it. Step mappings and Jinja template references are rewritten to use the new field name the next time the pipeline is refreshed. No manual reconfiguration is required.

What gets updated automatically

When Pipelines detects a rename, it applies two updates together:

• Step mappings—any step that maps a value to the renamed field continues to do so under the new field name, and the mapped value is preserved.

• Jinja template references—any {{ step.field_name }} reference to the renamed field, in any step across the pipeline, is rewritten to match the new name.

When the rename takes effect

Pipelines detects renames when it re-reads a step's fields from Quickbase. This happens in three situations:

Full pipeline refresh

Select Refresh Schemas in the pipeline editor to re-read the fields for every step at once. All renames detected across any step in the pipeline are applied together, including all Jinja template rewrites.

Use this option after making multiple changes in Quickbase, or to confirm the final state of a pipeline after any rename activity.

Single step refresh

Select Refresh on an individual step to re-read the fields for that step only. If a rename is detected:

• The renamed field appears in that step under its new name, with its mapped value intact.

• Jinja references to that field in all other steps in the pipeline are rewritten to match—even though those steps are not themselves refreshed.

This is the most targeted option. Only one step is re-fetched, but the rename propagates consistently across the whole pipeline.

Edits that trigger an automatic refresh

Some edits to a step cause Pipelines to refresh that step's fields automatically as part of saving the change. When this happens, any rename present at that moment is picked up and applied.

Edits that trigger an automatic refresh include:

• Adding or changing a field through the field selector

• Changing the step's options

Routine edits—such as adjusting a mapped value or modifying a Jinja expression directly—do not trigger a refresh and won't pick up a pending rename.

Example of renaming steps

Each step mapping in Pipelines has three parts: the Quickbase field being written to, the value mapped to it, and the Jinja template reference used to pass that value to downstream steps. The following example shows how all three update automatically after a rename.

A Create Record step in a Customers pipeline has the following mapping:

The field Account Owner is renamed to Customer Manager in Quickbase. After the next refresh, the step appears as follows—with no manual changes:

The mapped value Sales Team Lead is preserved. The Jinja template is updated to {{ a.customer_manager }}. Pipeline execution produces identical results.

Scope and limitations

• Pipelines continue to run between the rename and the refresh. If a field is renamed in Quickbase but the pipeline has not yet been refreshed, the pipeline continues to run on schedule and execute correctly in the meantime. The old field name remains valid until a refresh occurs.

• Refresh rewrites simple field references only. When a field is renamed, Pipelines automatically updates standard Jinja references such as {{ a.old_name }}. References embedded in custom Jinja expressions—logic or transformations written manually by advanced users—are not detected and will continue to use the old field name. Review and update these manually after a rename.

• Automatic rename detection applies to Quickbase fields only. Field renames in other channels may still require manual reconfiguration.

• If a field was renamed before the pipeline was last refreshed, the rename is still picked up. The next refresh detects and applies it, even if some time has passed since the rename occurred.

• No configuration data is lost. All mapped values, Jinja templates, and other references configured against the old field name carry over automatically under the new name.

Best practices

• Refresh after a known rename. While the update is automatic, open the pipeline and run a refresh after renaming a field to confirm the new name is reflected correctly across every step.

• Batch multiple renames before refreshing. If you're renaming several fields on the same table, complete all renames in Quickbase before returning to Pipelines. A single Refresh Schemas then handles everything at once, which is faster than refreshing between each rename.

• Concurrent edits are handled safely. If someone else renames a field while you're actively editing a pipeline, both the rename and your in-progress changes are reconciled automatically when you save and refresh the pipeline. No coordination with other editors is required.