Enhance the Multi-Level List (MLL) export functionality to include a unique parent-child linkage column that enables users to easily relate and reconstruct hierarchical relationships across the separate CSV tabs generated during export.

Why is it useful?

Today, when users export a Multi-Level List from Targetprocess, each hierarchy level is exported to a separate tab within the CSV/Excel output. While this preserves the hierarchy structure visually, it can be challenging for users to perform downstream reporting, analytics, reconciliation, and data integration activities because there is no direct field available to associate records between hierarchy levels.

Adding a linkage column would significantly improve the usability of exported data by allowing users to establish relationships between parent and child entities after export. This would reduce manual effort and eliminate the need for users to recreate hierarchy mappings outside of Targetprocess.

Who would benefit from it?

This enhancement would benefit:

• Portfolio Managers and PMO teams performing hierarchy analysis in Excel or BI tools.
• Reporting and Analytics teams creating custom reports and dashboards.
• Data Integration teams loading Targetprocess data into external systems.
• Enterprise customers with complex portfolio hierarchies who frequently export data for governance, planning, and audit purposes.

How should it work?

When exporting a Multi-Level List, users should have the option to include hierarchy linkage fields in the export.

For each exported entity, Targetprocess could include one or more additional columns such as:

• Parent Entity ID – the unique ID of the immediate parent entity.
• Parent Entity Name – the name of the immediate parent entity (optional).
• Root Entity ID – the top-level ancestor in the hierarchy (optional).

These columns would be included in every exported tab, enabling users to easily join datasets across tabs using common identifiers. For example, Features could be linked back to Epics, Epics could be linked to Initiatives, and so on, without requiring manual lookup or reconstruction of the hierarchy.