Transferring Project Data Using Custom Step: Example

This example demonstrates how to add and run a synchronization between two distinct environments of P6 application, and monitor the data transfer. For more details, refer to the P6 EPPM Data Migration Guide.

This example uses two P6 deployments:

P6 provider is installed for each deployed instance.

Goals:

Prerequisites

This example assumes the following prerequisites have been completed:

Move Data between Different Environments of an Application

  1. In the sidebar select Synchronizations and then select Add....
  2. In the Flow & Deployments step of the Synchronization wizard:
    1. In the Synchronization Name field, enter Synchronize Master Data from P6 Testing to P6 Production.
    2. Select Send Project Data Using Custom Step from the Business Flow list.

      Note: P6 deployments will be automatically selected from the Source and Destination lists based on the selected business flow.

    3. In the Description field, enter a description of the synchronization.
    4. Select Next.
  3. In the Parameters step:
    1. In the EPS Location parameter, enter the EPS ID for the project in P6 Deployment-Production.
    2. In the P6 Filter parameter, enter the projects to be sent using Project IDs, EPS IDs, Project Code Type Name, Project Code Value, or Project Code, and then select Add Row.
  4. In the Summary step, review a summary of all the updates made and then select Save.
  5. On the Synchronization page, select Run.

Monitor Synchronization Job

Check to see if the synchronization is working as expected:

  1. In the sidebar, select Monitoring.
  2. For the synchronization job, select the Job link.
  3. Select the Job Details tab expand each flow step to review the work done by the synchronization.
  4. Select Download to save the job details contained in each flow step as a zip file.

    If the job has a status of Failed, Completed with Errors, or Completed with Warnings, expand the failed step and view the log file containing the warning message or error message. The log files are generated in the format Warning_job#.log and Error_job#.log.

  5. Select the Data Details tab to review the objects transfered between the source and destination P6 deployments.

    Note: If you are an administrator or a user with no data access privileges, an error message, Insufficient Permissions, is displayed.



Legal Notices | Your Privacy Rights
Copyright © 2013, 2022

Last Published Thursday, October 6, 2022