Identifying the source project of data objects when data is exported from multiple PP files
You can use the Business Intelligence Controller to export data from one or more standalone projects or from projects that are stored in a data source on an Enterprise server.
If you export data from a single standalone project - a PP file - or from projects that are stored in a data source on an Enterprise server, all data objects belong to the same entity, so they each have a unique internal object ID. If you export data from multiple PP files, this is not necessarily the case; data objects in different PP files may share the same internal object ID. In order that any data objects that may share the same internal object ID can be distinguished from each other, the Business Intelligence export models that are supplied by default include the following information:
- The GUID and version number of the originating project. These will be unique, unless the PP files have been created by copying and pasting an existing project in Windows® Explorer.
- The name of the originating PP file, both as a long name with full path and as a short name with the simple file name (for server-mounted projects, the long name indicates the data source ID and project ID and the short name indicates the numeric project ID).
You can also use the short and long names of project summary objects to distinguish between different PP files if you wish - these fields relate to the Name and Short name fields on the Properties tab of the Properties dialog in Powerproject.
The following table describes the fields that you can use in a Business Intelligence export model to identify the source project of data objects:
| Column name | Project summary field | Description |
|---|---|---|
| PlanningDataID | projectguid | The GUID that is assigned when creating a new PP file. |
| PlanningDataVersion | projectversion | Starts at 0; incremented by 1 each time you Save As. |
| ShortName | shortname | The contents of the Short name field on the Properties tab of the Properties dialog. |
| LongName | longname | The contents of the Name field on the Properties tab of the Properties dialog. |
| ShortFileName | shortfilename | The name part of the PP file name; the numeric project ID for server-mounted projects. |
| LongFileName | longfilename | The full PP file name; the data source name and project ID for server-mounted projects. |
The following example shows how these fields could be used in a Business Intelligence export model:
<Table name="Task" apptype="task">
<Columns>
<Column name="PlanningDataID" datatype="GUID" group="Location" psfield="projectguid"/>
<Column name="PlanningDataVersion" datatype="Integer" group="Location" psfield="projectversion"/>
<Column name="ShortName" datatype="String" group="Location" psfield="shortname" size="120"/>
<Column name="LongName" datatype="String" group="Location" psfield="longname" size="120"/>
<Column name="ShortFileName" datatype="String" group="Location" psfield="shortfilename"/>
<Column name="LongFileName" datatype="String" group="Location" psfield="longfilename"/>
</Columns>
</Table>
Creating and compiling your own Business Intelligence export models
Understanding the structure and elements of projects
Finding the names of properties to include in a Business Intelligence export model
Adding columns to Business Intelligence export models
Deleting elements from Business Intelligence export models