Primavera-D365 Sync API
Budget: $750 – $1,500 USD
I need an API that bridges Primavera P6 Enterprise Cloud with the Projects module in Microsoft Dynamics 365 Business Central so that key project information stays aligned every day. The connector must pull data from P6 and push it into D365, and vice-versa if required, handling the three core data sets we rely on—project schedules, resource & assignment details, and all associated financial data.
The process should run on a daily schedule. A lightweight Basic authentication scheme is sufficient for both ends of the connection; credentials will be stored in our secure vault and injected at runtime. Performance is more important than real-time speed, but the job must complete well within our overnight maintenance window and log clear success or failure messages for monitoring.
Please design clean, versioned REST endpoints, include field-level mapping between the two systems, and build in idempotency so repeated runs do not create duplicates. Source code should be delivered in a private Git repo with concise setup instructions, and any third-party libraries or SDKs you select must carry standard permissive licences.
Deliverables
• API source code with unit tests
• Postman (or comparable) collection that demonstrates each endpoint
• Mapping document showing P6 ↔ D365 fields
• Deployment script or Dockerfile for staging and production environments
• Brief user guide outlining schedule configuration, log locations, and rollback steps
I will validate the work by running the sync in our sandbox and comparing records for completeness and accuracy across all three data groups.
The process should run on a daily schedule. A lightweight Basic authentication scheme is sufficient for both ends of the connection; credentials will be stored in our secure vault and injected at runtime. Performance is more important than real-time speed, but the job must complete well within our overnight maintenance window and log clear success or failure messages for monitoring.
Please design clean, versioned REST endpoints, include field-level mapping between the two systems, and build in idempotency so repeated runs do not create duplicates. Source code should be delivered in a private Git repo with concise setup instructions, and any third-party libraries or SDKs you select must carry standard permissive licences.
Deliverables
• API source code with unit tests
• Postman (or comparable) collection that demonstrates each endpoint
• Mapping document showing P6 ↔ D365 fields
• Deployment script or Dockerfile for staging and production environments
• Brief user guide outlining schedule configuration, log locations, and rollback steps
I will validate the work by running the sync in our sandbox and comparing records for completeness and accuracy across all three data groups.