Commit Transaction: Ends the current transaction.

You can make as many changes to the database as you want inside a single transaction, but keep in mind it will all be reverted unless explicitly committed via the 'Commit Transaction' script step. If the script ends before reaching the commit step, it will automatically revert the transaction.

Any changes in database records made after this step will be stored inside the transaction and will not be committed or reverted until the relevant transaction script step is called.

Open Transaction: This step initiates the start of the transaction.

While Filemaker has had the capability of performing transactions via scripts, in the past it involved manually setting up a transactional environment and database tables dedicated to transactions to help with performing this extremely useful action, Claris has added three script steps explicitly for use with transactions.

They are typically used for the mass creation, editing, or deletion of records where you want to ensure the entire set of data is valid, and if it is not, discarding the entire transaction as if the script itself never ran.

Transactions are an excellent way to bundle sets of actions together, executing them or reverting them as a whole instead of a several smaller pieces. Arguably the largest new feature that 19.6 brings to the table is built-in support for transactions.

Filemaker advanced