Skip to Main Content
InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Status Needs review
Categories InterSystems IRIS
Created by Rubens Silva
Created on Mar 31, 2026

Make the debugger skip classes without generated code

There's just no use on having the debugger jump inside classes that don't have generated code (such as %DynamicObject, %Api.Atelier, %RegisteredObject etc), causing it to fail and make the whole debugging procedure a hell.

Mind you that while we can theorically compile these classes after chaging the *LIB database to RW, some classes are still subjected to compilation errors due to the usage of routines that are not available for public viewing.

Therefore, since we can't actually know what is happening inside these methods just make the debugger ignore it altogether or provide us a way to actually see what is happening inside there if possible.

  • ADMIN RESPONSE
    Mar 31, 2026

    Thank you for submitting the idea. The status has been changed to "Needs review".

    Stay tuned!