Core package import overview

The core package import process lets administrators deploy Project Operations demonstration data into a Dynamics 365 environment by using Package Deployer. The process imports two predefined data packages that add setup and sample transactional records, so you can explore Project Operations scenarios, demonstrate the application, and evaluate its capabilities without creating representative data manually.

What core package import does

Core package import deploys two packages into your environment: PD - PO Core - Setup Data and PD - PO Core - Transactional Data. The Setup data package creates the foundational setup records that Project Operations scenarios depend on. The Transactional data package then adds sample transactional records, such as projects, that build on those setup records.

You must import the Setup data package before the Transactional data package. The transactional records depend on records that the Setup package creates, so importing the packages out of order causes the import to fail. After you import and validate both packages, your environment contains the setup and sample transactional records needed to use the Project Operations demonstration scenarios.

Steps in this process

Work through the following articles in order. Each article covers one step and ends by pointing you to the next one.

1. Prerequisites for core package import — confirm your sign-in role, internet access, and downloaded package files before you start.
2. Import the Setup data package — import PD - PO Core - Setup Data by using Package Deployer, and validate the result.
3. Import the Transactional data package — import PD - PO Core - Transactional Data by using Package Deployer, and validate the result.