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″]
End of Content.
Stay up to date with the latest news & examples from SeedCode
Unconference Sessions If you missed Pause in October, here’s a look at the sessions that attendees hosted. All the sessions are listed in this post
Subscribe to DayBack’s latest features and example code at our new site: updates.dayback.com You’ll find new features and documentation, as well as the status and
SeedCode’s Ann Kiser recently spoke to the Claris Beyond user group about her experiences running projects in Salesforce and how to use the Salesforce API
DayBack for FileMaker 19 works great in Claris Pro with no changes required. The older DayBack Classic also works in Claris Pro, but requires a few changes.
Stay up to date with the latest news & examples from SeedCode
© 2023 SeedCode, Inc.
2 Comments
Amen! Here is the tool we’re talking about: http://www.dracoventions.com/products/2empowerFM/family/developer.php
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