Welcome to the community Nori.
I can’t help but think you are overdoing it. Think of it as such please: An IDE is expected to offer debugging capabilities for the programming language features, not more. For example you cannot expect an IDE to offer you memory-allocation debugging capabilities if the language itself is garbage-collected with automatic memory management.
In Appsheet you don’t write Algorithms as in “Control Flows”, for you to need a debugger for it. You merely write expressions to calculate column values and you can base them on and encapsulate them in simple logical Yes/No expressions.
I’m new to Appsheet myself, less than a month, and managed to have a working application with complex functionalities based on around 30 tables in that period. I couldn’t say that I would have done it faster in a conventional you-code-everything platform.
Yes, it involved reading for dozens of hours, mainly topics in this forum, but the biggest obstacle was to adapt myself to a new way of thinking rather than burdening myself with my background and self-imposing it while working with AppSheet. When I surmounted this obstacle everything became easier and faster.
This is my advice to you.
Additionally, AppSheet editor tools are sufficient to find errors. Expressions can be easily tested using the expression assistant; it even translate the expression for you and lets you test it on all rows before you save it. There are few known-bugs but you’ll know when you run into one, and there is always this excellent community to ask for help.
If your question about debugging automation is a preemptive one, I strongly encourage you to put it aside and just start. If you have an automation that is not running as expected, this is almost always because of an error in your expression and/or misunderstanding regarding how its result would be interpreted. In this case share your problem with the community and you’ll find a solution and plenty of useful resources to read.
All the best!
LinkedIn
Twitter
