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 In Progress
Categories InterSystems IRIS
Created by Ricard Ferrando Paredes
Created on Jul 23, 2026

DTL Editor: Undo Action Collapses All Expanded Source/Target Field Trees

When working on a Data Transformation (DTL) with a complex HL7 message structure, I usually need to expand several levels of the source and target field trees (repeating groups, segments, components) to build and review my mappings comfortably.

The problem is that every time I use the Undo button after making a change, the entire source and target trees collapse back to their default state, losing all the expanded nodes I had open. This means I have to manually re-expand everything from scratch just to get back to the view I was working with, which significantly slows down development, especially in DTLs with many nested groups and long field paths.

Suggested improvement:

  • When undoing an action, the editor should preserve the current expand/collapse state of the source and target field trees, instead of resetting them.

  • It would also be very helpful to have a visible history of undone/redone actions (similar to an undo/redo stack list), so developers can see what was changed and quickly jump to a specific point in the edit history instead of clicking Undo repeatedly and guessing.

  • ADMIN RESPONSE
    Jul 23, 2026

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

    Stay tuned!

  • Brett Saviano
    Jul 23, 2026

    Hi @Guest , does this feedback apply to the classic DTL editor or the modern one? What IRIS version are you using?