Finding Scripting Errors

[FileMaker Magazine]

As any FileMaker solution grows, it's inevitable that errors will creep in as methods and scripts are updated with newer features. And with every new script you add, you're also introducing new opportunities for errors.

For the longest time, we've relied on the Pause on Error checkbox to invoke the debugger when an error occurs. While useful, the constant pop-up of the debugger can quickly interrupt your development "flow" — and honestly, it gets a bit annoying.

Starting with FileMaker 18, we gained a new script step called Set Error Logging. When used effectively within your script call stack, this step can be a powerful tool. By integrating it properly, you can capture and pass along exactly the information you want when errors occur. Even better, if you're logging to a terminal window, you can add color to make the output easier to scan.

This video will walk you through one of the best methods for catching and analyzing errors while scripting your FileMaker solution.

Click the title or link to this article to view the video.

View the full article