Export user data from Project for the web

Artykuł
07/07/2023

This article describes how a Microsoft 365 tenant admin can export a specific user’s data from Project for the web. The admin can then choose to view the user’s data and decide what data they want to make available to the user. The task data from Project for the web is synchronized with Planner to populate the user’s ‘Assigned to Me’ view in Planner. If you are solely interested in the project data, you can export it from Project for the web using the steps provided below. However, if you also wish to export the Planner-specific data associated with those project tasks, you can do so by exporting the data from the ‘Assigned to Me’ view in Planner.

Project for the web data is stored in Dataverse in Microsoft PowerApps. This article describes how you can:

View a specific user’s Project for the web data by using the Advanced Find function in Dynamics 365.
Use a PowerShell script to export data about specific projects that your user was a part of.

Requirements

You’ll need the following in order to look for data on a specific user through the Advanced Find search feature:

You need the Microsoft Entra Object ID (Microsoft Entra ID) of the user. You can find it in the Microsoft Entra Admin Center.
You need to be a global admin in your Microsoft 365 tenant. You need this to access the Dynamics 365 Admin Center.

If you also want to export and view information on specific projects:

You need to be a tenant admin.
You need to have a Project Plan 1, Project Plan 3, or Project Plan 5 license.

Methods for finding your user's data

Depending on the type of user data you need to find, there are two paths you can take in searching for and exporting your user's data.

Find data about your user's project and roadmap objects in Dataverse - Use the Advanced Find feature in the Dynamics 365 Admin Center to find all the user's data that is contained in Dataverse (for example, objects related to their projects and roadmaps).
Find data about specific projects that your user was associated with - Use the project export PowerShell script to get details about specific projects the user was associated with.

Find user data in Dataverse with the Advanced Find search feature

Project for the web user information that resides in Dataverse - such as roadmap and project objects and properties - are located in specific Dynamics 365 solutions. The Advanced Find search feature in the Dynamics 365 Admin center can query across entities in these solutions to find the information you need.

Understand Project for the web Dataverse data and where it resides

When looking for a specific user's Project for the web data in Dynamics 365 Dataverse, it’s located in these five Dynamics 365 solutions:

Name	Display Name
PortfolioService	Portfolio Service
msdyn_ProjectServiceCore	Project
MicrosoftDynamicsScheduling	Universal Resource Scheduling
msdynce_SchedulingPatch	Scheduling Patch
mydynce_Scheduling	Scheduling

You can look specifically at any of these Dynamics 365 solutions to get an idea of the entities that exist for it. Understanding the entities that exist for a specific solution can help you with understanding what to look for in your query.

To view entities for a Dynamics 365 solution:

In the Microsoft 365 Admin center, under Admin centers, select Dynamics 365.
In the Dynamics 365 Administration Center, select the default instance, and then select Open.
On the Dynamics 365 Settings page, select the Settings menu, and in the Customization section, select Solutions.
On the All Solutions page, select the Display Name of the solution that you’re interested in.
On the solution information page, expand Entities to view them.
Under each entity, you can select specific objects to get more details about its properties.

Use Advanced Find to search for user data

Use Dynamics 365 Advanced Find search to look for Project for the web data for your user. Advanced Find will search across all solutions in your Dataverse instance. You can then download the results directly to an Excel spreadsheet and determine what to provide to your user.

In the Dynamics 365 Administration Center, select the default instance, and then select Open.
On the Dynamics 365 Settings page, select the Settings menu, and in the Customization section, select Solutions.
Select the Advance Find button.
In Advanced Find, in the Look for menu, select the objects that you want to search for, such as your user's projects or roadmaps.

For example, if you want to view all roadmaps your user was a part of, select Roadmaps.
To begin building your query, select Select, and then select the fields you need to start searching for projects or roadmaps your user was a part of. You’ll need the users Microsoft Entra ID or account name.

For example:
- To find all roadmaps owned by the user, select the Owner field, and then select Equals, and then enter the account name for the user.
- To find all roadmaps created by the user, select the Created By field, and then select Equals, and then enter the account name for the user.
When you’re done with selecting your search criteria, in the ribbon, select Edit Columns.
On the Edit columns page, select Add columns, and then select the columns you want to include in the query. When done, select OK.
Select Results to run your query.
After you receive your results, you can export them to Excel. To do this, select Export, and then select Static Worksheet.

You can then review the results to determine what data you'd like to provide to the user.

Use the export script to see details on specific projects

If you need to look for more details that are contained in specific projects that the user was associated with, you can use the ExportProjectContent PowerShell script to get more information on each project. With the script, you can get the following files for a specific project:

Project files (.MPP) for the project. Add the parameter -mppexport $true to the cmdlet to generate .mpp files of the project plans.
An XML file that contains project details and settings.

Get the Project IDs of the projects you’re interested in

Before you run the script, you need to get the Project IDs of the projects you’re interested in.

Assuming you've used Advanced Find search to query for the user's projects and have downloaded them to an Excel file, the Project ID column is the first column of the Excel spreadsheet, but it’s hidden by default. Unhiding the first column can be a bit tricky, so if you need help, see Unhide the first row or column in a worksheet.

After you unhide the columns in the spreadsheet, look for the name of the project, and then look for the corresponding value in the Project column to find the Project ID for the project.

Dataverse Instance.

Run the Export script

Now that you have the Project IDs of the projects you’re interested in looking at, use the ExportProjectContent Windows PowerShell function to get more information. The ExportProjectUserContent function is included in the ProjectExport Windows PowerShell module.

Download the Project Export Windows PowerShell module and first unblock the zip file and then unzip the files.

Note

After you unzip the script, run the following in Windows PowerShell to import the modules:

Import-Module -Name ./projectexport

To run the ExportProjectContent function:

In Windows PowerShell, where you’ve imported the module, run the following cmdlet:

ExportProjectContent -ProjectId (ProjectID of the project) -OutputDirectory (Location to put files) -InstanceId "(Dataverse instance name)"

You’ll need to configure the following parameters when running the script:

Parameter	Description
ProjectId	GUID of the project within Dataverse. You learned how to find this in the previous section.
OutputDirectory	Location where the export files are put.
InstanceId	The identifier of the Dynamics 365 instance you’re using.

To find your Instance ID:

In the Dynamics 365 Administration Center, select the default instance, and then select Open.
On the PowerApps setting page, look at the first part of the URL to determine your Instance ID value. In the graphic below, the Instance ID value would be https://orgde6d15d8.crm.dynamics.com.

As an example of how to run the script, if the Project ID of the project is dd065460-02b8-e911-a989-000d3a170e10, you want the output files to go to C:\User1Project1, and the instance name of the Dataverse org is https://orgde6d15d8.crm.dynamics.com, you would run the script like this:

ExportProjectContent -ProjectID dd065460-02b8-e911-a989-000d3a170e10 -OutputDirectory C:\User1Project1 -InstanceId https://orgde6d15d8.crm.dynamics.com"

When the script completes, go to the OutputDirectory location you specified to find the .json files for the project.

3a215ea2-c650-49db-8200-47bd4a7e2278_2023-02-13T21-29-13Z.json

If you have multiple projects, run the script again for each project, using its corresponding ProjectID value.

Note that you may receive multiple versions of your .json file, known as snapshots. These are versions of your project file prior to changes being made to it. Snapshot files will include a timestamp to let you know when they were taken. The current version of the file is the one with the earliest timestamp, which would be the project creation date.

All snapshots currently stored for the project are exported. Snapshots can be periodically cleared out depending on how active the project is.

The field definitions are at Export Content Definition.

View and export Project History

Open the Advanced Find tool. In the Look for menu, select the Project History object.

If you want to filter on a particular project, choose Select, select the Project option from the drop-down dialog, and then add the project for which you’d like to see Project History items.

When you’re done with selecting your search criteria, in the ribbon, select Edit Columns.

On the Edit columns page, select Add columns, and then select the columns you want to include in the query. When done, select OK.

Select Results to run your query.

After you receive your results, you can export them to Excel. To do this, select Export, and then select Static Worksheet.

Use the Power Apps portal to view the descriptions of the different fields that are stored with the Project History data. Open the Project History table within the msdyn_ProjectServiceCore_Patch solution. The msdyn_project field is a reference to the related project. msdyn_projecttask is a reference to the associated task (if applicable). The msdyn_details field is a JSON object that describes the details of the history record. More information on what is contained in msdyn_details can be found in the Task History Definition.