Tip: Debugging Using GoZync’s Logs

Working on a GoZync integration with Jason this morning and remembered this troubleshooting trick Todd and I came up with. This lets you quickly find where a given operation happens in GoZync scripts. (Worth a quick watch.)

[ba-youtubeflex videoid=”JJvDaqFiZx4″]

Featured Posts

Follow Along

Stay up to date with the latest news & examples from SeedCode


  • Arild Schönberg

    Thank you John. I use the “Developer Assistant” from 2empowerFM every day in just this manor. When trouble shooting scripts for IWP, there is no way to step through the code, so I have a script that writes a short log text to the session table for every place in the script where something could go wrong. This way I can follow the session in FMP as I trigger the scripts in IWP in the browser.

    When the script stops giving comments, I can easily track the script with the log text from the session record.

    We always number our scripts too, so tracking the script is really easy as the script no. is in every log line.

    Developer Assistant is an awesome tool and I can’t imagine writing code in FileMaker without it.

    /Arild Schonberg, Re-Base Stockholm

Leave a Reply

Your email address will not be published. Required fields are marked *

Check out some of our other posts ...

Comments in FileMaker Calendar

Highlight Notes and Comments in Your Calendar

Inline Notes in DayBack Calendar The latest DayBack extension adds an icon to your events when there is a comment present that matches your criteria. You can

Closed Through the New Year

SeedCode is closed for our holiday break from December 19th through the end of the year. We’ll have folks available in case of emergencies and



Stay up to date with the latest news & examples from SeedCode

© 2023 SeedCode, Inc.