Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2024-10-11
Troubleshooting: Migrate Workforce Planning Application Using Object Transporter

Troubleshooting: Migrate Workforce Planning Application Using Object Transporter

Migration fails.

Some objects in your workforce planning application package are missing their Reference ID.
Add Reference IDs to those object instances.
  1. On the error message that we display after the failed import, copy the instance IDs of objects that don't have a Reference ID.
    Example: We display this error message: Your Package cannot be migrated as some instances do not have a Reference ID in the source tenant. The instances (referenced by their WID) are: [ce6b374cf2441043113792cc50056, cd210bdedf831006ff4617a0e99700cd]. You can retry your migration once all instances have a valid Reference ID.
    Copy these instance IDs:
    • ce6b374cf2441043113792cc50056
    • cd210bdedf831006ff4617a0e99700cd
  2. In the source tenant, access each copied instance ID using global search to review the business object for each object instance.
  3. Access the
    Maintain Reference IDs
     task.
    Security:
    Set Up: System
     domain in the System functional area.
  4. Select the business object for the object instance that’s missing their Reference ID.
  5. (Optional) To review the ID naming pattern and which IDs already exist, select
    None of the above
     to view all object instances for this business object.
    If you review all object instances with Reference IDs, you might save time when you enter new IDs.
  6. Enter a
    Reference ID Value
     for the object instance that’s missing their Reference ID.
  7. Try migrating the application from your source tenant to your target tenant again.
A calculated field exists in both the source and target tenant with the same name, but different Reference IDs.
Delete the calculated field in the target tenant. When you try migrating again, this calculated field now uses the same name and Reference ID in both the source and target tenants.
The name or purpose of the planning configuration manager on your source tenant doesn’t match the name or purpose of the planning configuration manager on your target tenant.
Create a new planning configuration manager on your source tenant with the correct name and purpose, then try migrating again. We don’t currently support changing the name or purpose of existing planning configuration managers.
The user who creates and saves the planning configuration manager in the source tenant doesn’t have access to the
Custom Report Creation
 domain in the System functional area in the target tenant. The object transporter requires this user to have access so that we can migrate data and metadata.
Give this user access to the
Custom Report Creation
 domain in the System functional area in the target tenant.
See Edit Domain Security Policies.
Changed WIDs caused mapping conflicts for the data and metadata loaders in Adaptive Planning following a migration from Implementation to a Production or Sandbox tenant.
Clear your external mappings and run the SYS-HPA metadata loader task and SYS-HPA data loader task in Adaptive Planning Design Integrations.
  1. Navigate to Modeling > Model Management and select Clear External Mappings.
    This removes mappings when Workday IDs (WIDs) changed and caused mapping conflicts after a tenant migrated from Implementation to Sandbox or Production.
  2. Navigate to Design Integrations in Adaptive Planning and run the Orchestration task.
  3. Run the SYS-HPA metadata loader task.
  4. Run the SYS-HPA data loader task.

Can't change report field for a column between migrations.

You migrated a headcount planning application between your source and target tenant. On your target tenant, you change the report field for a roster sheet column. The next time you migrate this application from the same source to the same target, on the target tenant the application:
  • Retains the column with the changed report field.
  • Adds a new column with the old report field.
We don't currently support deleting parts of the object during migration.
Unregister the workforce planning application, update the report field in the workforce planning configuration manager, then initiate the migration.
  1. In Adaptive Planning, select
    Integration
    Design Integrations
     from the main menu.
    Security:
    Data Designer
     permission.
  2. Select the Workday credential that you use for headcount planning.
  3. Select
    Unregister Orchestration
    .
    Keep this browser tab open.
  4. On a new browser tab, in your Workday source tenant, access the
    Manage Workforce Planning Configuration
     task.
    Security: domain in the functional area.
  5. Select
    Edit Existing Application
    .
  6. Select the application where you want to change the report field for a column.
  7. Navigate to the
    Roster Sheet
     page.
  8. Change the
    Field
     selection on your column.
  9. Select
    Next
    .
  10. On your Adaptive Planning browser tab, select
    Register Orchestration
    .
  11. On your Workday browser tab, navigate to the
    Review Changes & Activate
     page.
  12. Activate the application.
  13. Try migrating the application from your source tenant to your target tenant again.