I am trying to find a way to debug a logic block that is invoked by a table row insert/update trigger. Can I use no-code platform to do it? Meaning to set breakpoint, inspect variables, etc.
Hi David!
Yes. You should be able to select the “Save” action for debug, which will debug all triggers that run during your save of the record. From there, it’s easiest if you already have a breakpoint set at the beginning of the trigger you want to see debugged specifically; then you can just click Run and it will run until it hits the breakpoint at the start of your logic block. From there you can debug as normal.
5 Likes
Of course, Brendan beat me to it.
1 Like
Thanks for the advise; I am able to debug my logic block by building a test application that associates to the table and adding a row action to trigger the call to the logic block. Yeah, Save also works!
Test applications with row actions directly to the trigger are great for stepping through the logic easily (and the same concept can be applied to logic that otherwise runs in the background, like workflow logic or report execution logic). One thing to note is that by doing this and accessing a record from a Detail view of the test application, the logic will always run in NATE where it might not in the standard processing.
It’s also possible for transactions to update multiple records in one or more tables. When this happens, table triggers will execute in the order in which they were queued by the logic[1]. If your logic updates multiple records in the same table, setting a Breakpoint will take you to the first instance of that Trigger execution and not necessarily the record you expected to see, so it is occasionally necessary to step through the logic flow manually to better understand it.
This is true when NATE is on. When NATE is off, the triggers execute immediately on Update/Insert ↩︎