Debugging PL/SQL in IFS Cloud

Easiest way would likely be to add trace_sys.message calls (rather than dbms_output) in the bits of the code you want to debug/troubleshoot.

Then you can simply use the DevTools link to see your trace calls when performing an action.

(stealing ​@dsj ‘s screenshot here):

Indeed, this would likely need to take place in the Build Place. Theoretically, you could always add some trace_sys messages through PL/SQL Customizations, and deploy them to the Use Place as deliveries, but that’s a lot of work just for debugging.

Modifying the direct PLSQL code in the use place is probably possible if you’re using an on-prem install and have access to IFSAPP credentials, but if you’re cloud managed, IFS only gives you access to IFSINFO credentials which is fully read only and would not let you modify/recompile PLSQL packages in the use place.

Theoretically there are ways to do it in the Use Place in managed cloud installs but these ways are basically a hack and unintended by IFS R&D so I won’t discuss these publically, as these could be patched at any point.

Thanks for the response. I should have been a bit more clear on what I’m hoping to accomplish. I’m using the Oracle SQL Developer Extension for VSCode to write and test my PL/SQL code. It would be really cool if I could debug using the approach demonstrated here but it doesn’t appear to be possible as I can’t create the ACL. But thanks for the reference to Trace calls. That will be useful when/if there’s something unique to our Use Places.

Debugging PL/SQL with the Oracle SQL Developer Extension for VS Code