OX Composite Report Migration Fails: "Specified_Hierarchic_Reference" Validation Error
What it means
A Composite Report migrated with Object Transporter fails on a specific row's hierarchic reference, even though every sub-report and dependent object migrated fine. The fault's XPath points at a row inside the report's region data, but gives no readable detail about why. The real cause is usually a misconfigured row that Workday already flags as a migration risk in the UI, just not inside the OX fault itself.
Troubleshooting
- Read the fault's XPath (in the detail block) to identify which row index inside the report's Composite_Report_Region_Data is failing.
- In the source tenant, open the report and use Related Actions > Print (or Preview) rather than trying to debug from the OX error alone. Workday shows a distinct warning banner listing exactly which rows have misconfigured filter criteria that could impact migration.
- For each flagged row, check whether its underlying reference (a Ledger Account Summary, cost center hierarchy, or similar) is fully configured, for example a Ledger Account Summary with no Ledger Accounts assigned.
- Fix or remove the misconfigured row and re-run the print preview to confirm the warning clears before re-attempting the OX migration.
Open the report in the source tenant and check Related Actions > Print for a migration-risk warning naming the specific row, then remove or fix that row's reference (for example a Ledger Account Summary with no accounts assigned) and re-run the migration.
Before migrating any Composite or Matrix report with Object Transporter, check the report's Print or Preview output in the source tenant first, since Workday's own migration-risk warnings there are far more specific than the SOAP fault OX ultimately throws. Add this check to the migration runbook rather than debugging blind from the XPath.