Object Transporter Migration Fails: Custom Report ID Contains Spaces
What it means
Object Transporter identifies the custom report being migrated by its Custom_Report_ID, which Workday derives from the report's name. When the report name contains spaces or other characters that don't survive ID generation cleanly, the derived ID string gets rejected as an invalid ID value even though the report itself is a valid, existing object.
Troubleshooting
- Confirm the fault is on Custom_Report_ID specifically, and note the exact string OX is trying to use as the ID, it's usually the report's display name verbatim, spaces included.
- Check the report's name in the source tenant for spaces, punctuation, or special characters, these are the most common cause of a Custom_Report_ID mismatch during OX migration.
- Confirm whether the target tenant already has an object with a similarly derived ID that conflicts, or whether the ID simply never resolves because of the characters.
- If your OX tooling supports it, try referencing the report by an unambiguous identifier (its WID) in the migration package instead of relying on name based ID resolution.
Rename the report to remove spaces and special characters before re-running the Object Transporter migration, then rename it back afterward if the original name matters.
Adopt a naming convention for custom reports that avoids spaces and special characters for anything that will ever be migrated with Object Transporter, or standardize on WID based references in migration packages so report names can stay human friendly without breaking ID resolution.