Dependency Map

Use this as a planning aid, not as an installation runbook. Confirm the exact deployment steps against Microsoft documentation for the selected model.

Dependency rules

Dependency	Applies to	Evidence
Deployment model selected	All	Decision record and Microsoft deployment guidance.
Environment supports chosen apps	All	Environment details, installed apps, region and licensing evidence.
Legal entities identified	Integrated ERP and manufacturing; sometimes Core for design context	Finance company evidence and client operating model.
Organisational units and price lists defined	Core and Integrated ERP	PjO settings, cost price lists and currency evidence.
Dual-write prerequisites complete	Integrated ERP	Installed solutions, refreshed entities, installed maps and map health.
Security model agreed	All	Business units, roles, teams, users and access test evidence.

Configuration order matters

Configuration records often depend on deployment type, legal entity, currency, price list, security and integration prerequisites. Capture failed dependency assumptions as findings, not just setup errors.

Primary Microsoft documentation

• Determine your deployment type
• Deploy Project Operations Core
• Manually deploy the Project Operations Dataverse app with dual-write support
• Install Project Operations dual-write map versions