Modify Record

Use the Modify Record step to update fields on an existing record. The step takes a reference to the record (typically the rec output of an upstream Find Records or Insert Record step), applies the field values you list, and saves the record.

Configure the step

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

Description

• Purpose: Make it clear which record this step updates 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 Mark order as processed.

Reference

• Purpose: Identifies the record to modify.
• When to fill it: Required. Pick a SmartField that resolves to a record — for example the rec output of a previous step, or a path like prevStep.rec.
• 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. The configured table also drives the Field Values picker — fields are filtered to that table.
• Tips: If the reference resolves to a different table when the step runs, the step stops the flow with a configuration error.

Run Triggers

• Purpose: Decide whether BC's standard modify logic runs around the change — its validations and the table's OnModify trigger.
• Options:
  • On (default) — full BC behaviour. Validations fire and OnModify runs.
  • Off — the changes are written as-is, without validations or trigger code.

Field Values

Same shape as Insert Record's field list — including the Input Format column for values arriving in XML/JSON notation or as compact dates (see Insert Record → Input format) — with one difference: the field picker filters out primary-key fields. Listing a primary-key field is rejected when the step runs — use a Rename Record step to change keys.

Empty list. A Modify Record step with an empty Field Values list reads the record and re-saves it. That's useful when you want to re-run validations or trigger OnModify without changing anything yourself.

Binary fields (Blob, Media). Blob and Media fields are accepted as targets — same shape as the Binary fields section in Insert Record. Drop a {{pdfBody}}-style SmartField into the Value cell and the bytes go straight into the field.

Record ID fields. Fields of type Record ID take a single record reference in the Value cell ({{rec}}, {{results}}, …) — same shape as the Record ID fields section in Insert Record.

Outputs

Name	Type	Meaning
rec	Reference	The modified record.

Notes

• Partial updates. Only the fields you list are touched. Other fields keep their existing values.
• Validate ordering. Same as Insert Record: validations fire in row order, so a row that depends on another should come later.
• Type-conversion errors. An unparseable value ("abc" into a Decimal field, for example) stops the flow at this step. For values in XML/JSON notation or compact date layouts, set the row's Input Format instead of reformatting the value upstream.