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
Show Available Slots that Match Multiple Criteria Schedulers often look for gaps in their schedules to find the open resources for each opportunity. But sometimes,
Following up on this idea that people stretch themselves when they feel a little safer, we’ve been very focused on the customization experience for DayBack
Resource Scheduling Swimlanes You can now extend the pivoted scheduling view in DayBack to show items by week instead of solely by day. This lets
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
(855) SEEDCODE
Stay up to date with the latest news & examples from SeedCode
© 2024 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