Replace Field Contents safely in FileMaker scripts

Beginner

Use Replace Field Contents for bulk field updates with confirmation guards, found-set scoping, and rollback planning to prevent mass data overwrites.

What you'll learn

How Replace Field Contents works and why it is powerful
How to scope the found set deliberately before replacing
How to confirm the operation count before proceeding
How to use the serial number, calculation, and literal value replacement options
When to prefer a Loop + Set Field pattern instead

Replace Field Contents updates a field in every record of the current found set in a single operation -- making it extremely fast and extremely dangerous. A stray Show All Records before the step, or forgetting to scope the found set, can overwrite thousands of records. This lesson covers the guards and validation steps that make Replace Field Contents safe to use in production scripts.

1/3

Scope the found set before replacing

Never call Replace Field Contents on an untrusted found set. Always perform an explicit find or constrain operation to build the exact set of records you intend to update, then confirm the count with a dialog.

FileMaker Script

# Scope: only update invoices for one client that are still pending
Enter Find Mode [ Pause: Off ]
Set Field [ Invoices::ClientID ; $clientID ]
Set Field [ Invoices::Status ; "Pending" ]
Perform Find [ ]

If [ Get ( LastError ) = 401 ]
  Show Custom Dialog [ "No pending invoices found for this client." ]
  Exit Script [ Text Result: "none" ]
End If

Set Variable [ $count ; Value: Get ( FoundCount ) ]
Show Custom Dialog [
  Title: "Confirm Bulk Update" ;
  Message: "Update " & $count & " pending invoices to Approved?" ;
  Button 1: "Update All" ; Button 2: "Cancel"
]
If [ Get ( LastMessageChoice ) != 1 ]
  Exit Script [ Text Result: "cancelled" ]
End If

Import Records automation in FileMaker scripts Send Mail via SMTP using Insert from URL