Earlier in the month, I presented on Script Transactions as part of a Claris Community Live with Rosemary Tietge and Connor Brock from Claris. I really enjoy sharing my insights with the rest of the Claris Community (which is why I also run a Training Day session every year at Claris Engage). This presentation, in particular, was a great opportunity for me to provide other FileMaker users with an in-depth look at Script Transactions.
Script Transactions significantly improve the reliability and performance of your FileMaker applications. They allow developers to clump record changes together to ensure that they’re committed/reverted as a batch.
My experience has been that most developers know Transactions exist, but they don’t use them systematically. In my presentation, I shared how and why to use Script Transactions in hopes of encouraging these developers to feel more comfortable with Script Transactions and adopt them in their development workflows.
In the presentation, I discussed the following:
- An in-depth definition of Script Transactions
- How and why they work
- Concerns to consider, including data hygiene, data issues, business logic, and more
- Core concepts of error prevention
- Advanced topics, including multiple windows, subscripts, and error logging
- Expert-level tips and tricks
I encourage you to watch the recording to get all of the details.
Get the Demo and Slides
You can also download my slides and demo file if you’d like.
More FileMaker Expertise
I work with an entire team of FileMaker developers with expertise all areas of the platform. If you have any questions on how to improve your FileMaker application’s development, design, and deployment, contact our team to talk with a consultant best suited for your custom needs.
