Skip to main content

Rename Record

Use the Rename Record step to change the primary-key fields of an existing record. This is a separate step from Modify because BC handles renames differently — it relocates the record and updates references in other tables along the way.

Configure the step​

Open the flow editor, add Rename Record, and fill in the configuration card.

Description​

  • Purpose: Make it clear which record this step renames and why.
  • When to fill it: Always. The description shows up in the editor and the execution history.
  • Tips: Name the table and the intent, for example Renumber item to new scheme.

Reference​

  • Purpose: Identifies the record to rename.
  • When to fill it: Required. Pick a SmartField that resolves to a record — for example the rec output of a previous step.
  • Tips: SmartField references are entered through the picker, in the standard {{name}} notation – paste the placeholder as-is.

Table​

  • Purpose: The table the Reference is expected to point at.
  • When to fill it: Required. Validated against the resolved reference when the step runs.

New Primary Key Values​

The list is primary-key only and is prefilled with one row per primary-key field of the configured table. Fill in the new value for each key field. The Validate column from Insert / Modify is hidden here — BC always runs the table's OnRename trigger, there is no toggle.

Outputs​

NameTypeMeaning
recReferenceThe renamed record (with the new primary key).

Notes​

  • All key fields required. If any primary-key field is missing a value, the step stops the flow with a configuration error.
  • Up to 16 key fields. BC supports up to 16 primary-key components — that covers every standard table.
  • Key collision. If a record with the new primary key already exists in the table, BC stops the rename with an error.
  • References after the rename. Downstream steps that captured the rec output from before the rename hold a stale reference. Use the new rec output of this step instead.