Download as PDF, PPTX
![Allow User Abort [Off]
Doesn’t make sense for users to be able to escape
a script.](https://image.slidesharecdn.com/scriptingpresentation-161116130403/85/FileMaker-Scripting-Best-Practices-11-320.jpg)
![Set Error Capture [On]
Detailed error messaging empowers the user and
helps the developer troubleshoot](https://image.slidesharecdn.com/scriptingpresentation-161116130403/85/FileMaker-Scripting-Best-Practices-12-320.jpg)
Uploaded byDB Services
FileMaker Scripting Best Practices
The document provides best practices for scripting by Emory Brown, an application developer at DB Services, emphasizing clarity, readability, and error trapping in code. It encourages standard conventions to enhance code efficiency and foster user trust while addressing the importance of commenting and proper context. Additionally, it touches on the benefits and pitfalls of modular code and offers tips for naming variables effectively.
More Related Content
Similar to FileMaker Scripting Best Practices
FileMaker Scripting Best Practices
- 1. SCRIPTING BEST PRACTICES EmoryBrown Application Developer https://www.dbservices.com
- 2. Questions If you havea question, please typist it into the console. If we don’t get to your question, please send it to fba@dbservices.com
- 3.
- 4. About DB Services •Weare a team of analysts, developers, and designers creating custom applications to make your organization more effective and efficient. Learn more about our FileMaker services on our website. •If you leave this presentation wanting learn more! Check out our FileMaker Blog where we post new content each month. •To learn more about DB Services, check out our website at www.dbservices.com
- 5. Background Work Read more onme on our website, https://www.dbservices.com/, in the About section • Application Developer at DB Services • Certified in 15, 14,13, 12, 11 • Working with FileMaker for 6 years • Sponsor at FileMaker Developer Conference • Member of FM Academy • Global presence (Canada, Europe, Africa, South America) • Team focused on adding value
- 6. Scripting When coding, choosetwo: • It works • Easy to read • Quick to write Conventions help make code that works, faster to read and write.
- 7. Time Saving Humans arethe most expensive part of the application development cycle. • Template • Conventions • Scannable Code
- 8. Proper Context Ensure scriptis run from intended contexts • Saves time testing • Create fewer bugs • Generic scripts
- 9. Error-Trapping Scripts Three usefulsub-scripts to consider in every script • Halt of not in browse mode • Halt if no records in found set • Commit record and halt if invalid*
- 10. Error-Trapping Why Error trap? •Empower users • Speed up troubleshooting • Create user trust **Don’t make generic error messages
- 11. Allow User Abort[Off] Doesn’t make sense for users to be able to escape a script.
- 12. Set Error Capture[On] Detailed error messaging empowers the user and helps the developer troubleshoot
- 13.
- 14. Error-Trapping What to trapfor • New Record • Delete Record • Set field • Go to related record* • Interacting with systems outside of FileMaker
- 15. Commenting Not all commentsare created equal • Readability • Clarity • Scannability
- 16. Commenting Readability • Housekeeping • SectionHeaders • Spacing • Notations
- 17.
- 18.
- 19.
- 20.
- 21. Commenting Clarity vs Noise •Anything being used in a non- conventional way* • Stacked objects • Sort script steps*
- 22.
- 23. Commenting Most important thingis DOING IT • Update comments as you code • Create a template script with sections
- 24. Modular Code Pros &Cons • Can save time testing or updating • Can also add time to later updates • Don’t over-engineer
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. Evaluate Dangers of Evaluate() • Tempts you to hardcode field names • Slower than native code • Security risks
- 31. Tips & Tricks ScriptDebugger • Step-Into debugger • Turn off script trigger button
- 32. Naming Code How toname variables well • Self-describing noun • Unique name • NO right answer
- 33.