OX Custom Report Migration Fails: "Data_Source_Filter_Reference" Validation Error
What it means
Migrating a custom report with Object Transporter fails on the report's filter reference field, even though the report itself is valid and web-enabled in the source tenant. The filter is secured by a domain and functional area that Workday checks during migration, and if that domain or functional area isn't enabled the same way in the target tenant, the filter reference resolves to something the target considers invalid.
Troubleshooting
- Confirm the failure is specifically on the filter reference (Data_Source_Filter_Reference in the fault text), not the report definition itself. This narrows the cause to the filter's security, not the report's fields or calculated fields.
- Identify which functional area and domain secure the datasource filter used by the report (for example a Supplier Filter) in the source tenant.
- Check whether that same functional area is enabled in the target tenant. A functional area disabled in a sandbox or newer tenant is a common and easy to miss cause.
- Check the domain's security policy in the target tenant to confirm it's enabled and secured to the migrating account's group the same way it is in the source.
- If the security configuration matches and the error still occurs, this can be a known Workday migration gap where filter security isn't ignored during migration the way report security already is. Log a support case describing this if analysis doesn't resolve it.
Enable the functional area (and confirm the domain security policy) backing the report's data source filter in the target tenant, then retry the migration.
Before migrating any custom report between tenants, confirm the functional areas and domains behind every filter the report uses are enabled in the target tenant, not just the report's own security. Track recurring cases with Workday support so filter security gets the same migration handling report security already has.