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.)

Tagged with →  

2 Responses to Tip: Debugging Using GoZync’s Logs

  1. Arild Schönberg says:

    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 *

Share →
DOWNLOAD
DayBack Calendar
DayBack's 30-day trial is unlocked so you can customize it and integrate it with your files.
Download DayBack and we'll send you a couple short emails with tips on how to modify it and use some of the coolest features.
Thank you! Please download: DayBack Calendar
Need More?
SeedCode tips & example files in your inbox
Need More?
SeedCode tips & example files in your inbox
Want More?
Be the first to see articles and tips like these
DOWNLOAD
TimeZync
Download TimeZync and we'll send you a couple short emails with tips syncing your FileMaker Go files.
Thank you! Please download: TimeZync
Want More?
Be the first to see articles and tips like these