Define Data Mapping
Data mapping establishes a 1 to 1 association between fields in a Unifier schedule sheet and a schedule sheet, such as Primavera P6. The data map creates a CSV or XML file into which the data from the external schedule can be loaded. Once loaded with data values, these files can then be imported into a Unifier schedule.
You can create multiple data maps and select the data mapping you want to use when you import the schedule files to create or modify schedule sheet activities.
Note: You must create at least one mapping. Unifier will use this mapping as a default if there are no others.
Unifier supports multiple data formats: CSV, MPP, MPP XML, P6 XML. You must map any specific fields from an external source that you want to see in the application.
Data format | Data mapping requirements |
---|---|
CSV | Requires mapping; you can select the mapping when you upload the file. |
MPP | Mapping is not required. Imported fields are limited to Start Date, Finish Date, and Duration. Do not select a default data mapping if you will be asking Unifier to consider an activity calendar. |
Primavera XML | Requires default data mapping. |
Microsoft Project SML | Requires mapping; you can select the mapping when you upload the file. |
To define data mapping
- Go to the Company Workspace tab and switch to Admin mode.
- Click Templates in the left Navigator.
- In the left Navigator, click Templates > Shells > [shell type] > [shell template] > Schedule Manager > Schedule Sheets.
- From the Schedule Sheets log, open the Schedule Sheet template you want to map.
- Choose File > Data Mapping. The Data Mappings window opens.
The Data Mappings window lists any mappings created for schedules such as Primavera P6 or Microsoft ® Project.
If a mapping on this list is marked as the default mapping, Unifier will use this mapping when the schedule is imported. If you do not mark a mapping as the default, Unifier will prompt the users to select a mapping whenever they import a schedule.
- Click Add. The Data Mapping window opens.
- On the General tab, enter the name and the description for the data mapping and click Apply.
- Click the Activity tab.
Use this tab to create the structure of the CSV or XML file for the export and import operations. On this tab, you can map schedule sheet columns to external CSV headers and XML tags in order to import or export activity information.
- Click the Add button. Another data mapping window opens.
- Use the information in the first table below to complete the fields on this window.
- (Optional) On the Resources tab, you can map resource information through XML integration. Enter the header in the XML element that corresponds to the column.
Note: Mapping resources is mandatory only if you select Import Resource Assignments on the Options tab.
- Click the Add button. Another data mapping window opens.
- Select the column and enter the header in the XML element that corresponds to the column.
- Click Apply on the Resources tab.
- Click the Options tab. On this tab, you can configure XML options that are used when importing data.
- Use the information in the second table below to complete the fields on the Options tab.
- Click OK.
Data format | Data mapping requirements |
---|---|
Column | Select the data elements you want to import. Minimum required fields for XML import are Activity ID, Activity Name, Start date, Finish date, and Duration. |
CSV Header | Enter the CSV header from the external source. |
XML Element | Enter the XML from the external source |
In this field: | Do this: |
---|---|
XML Import | Define options for importing XML activity schedules into Unifier. Importing data, from the Unifier Schedule Sheet, supports Microsoft XML, only. The P6 XML is supported through Web Services. |
Options | You can either retain existing schedule information in Unifier, or overwrite it complete upon importing an external XML file.
|
Data Elements | Select the appropriate checkboxes if you want to import activities (rows), Activity Dependencies: Select this checkbox to retain activities from the XML source file. Activity Calendar: Select this checkbox to retain the activity calendar from the XML source file. If imported, the activity calendar will trigger the recalculation of activity dates as needed, and will override any existing activity calendar association. If a calendar is not imported, the activity will use the existing calendar defined in the Schedule Sheet properties. Note: There must be a calendar in Unifier with the same name as the calendar in the import file. Resource Assignments: Select this checkbox to retain the resource assignments from the XML source file. If you want to import resources, define the resource types for the data definition SYS Resource Type. For Microsoft Project files, use standard resource types: Work, Material, and Cost. Upon import, these resource types will soft book. CBS Codes: Select this checkbox to import CBS codes. See CBS code options for Primavera XML and Microsoft Project XML. Number of Levels: (for Primavera XML only) Specify the segments that should be considered in the Primavera XML file for the codes (from 1 to 9) and the CBS code suffix mask. See CBS code options for Primavera XML and Microsoft Project XML for details. Suffix Mask: (for Primavera XML only) You can use a constant or a data element value in the Suffix Mask.
|
XML Export | Define options for exporting through XML into another application |
Data Elements | Select the appropriate checkboxes if you want to export activities (rows), and whether to include dependencies, resource assignments, and/or CBS codes. |
CBS Code Options for Primavera XML and Microsoft Project XML
Unifier can recognize the CBS codes imported through XML files and match these codes to equivalent codes in a project/shell cost sheet. For Primavera XML files, you need to specify the Number of Levels and a Suffix Mask. (The codes in Microsoft Project XML files are automatically resolved by Unifier when the file is imported.)
The number of levels specifies the number of segments that should be included to build CBS codes based on data from the Primavera XML file. The number of segments considered starts from the top of the imported XML file. If you specify a number of segments and the data in the XML file has fewer segments than that number, then all segments are processed.
The Suffix Mask you enter is added to the CBS code elements that Integration derives from the XML file. The CBS code derived from the XML file with the mask is validated against the CBS codes (leaf level) created for the project/shell Cost Sheet.
While deriving the CBS codes from the XML file, Integration separates segments retrieved from the XML file with the cost code separator specified in uDesigner). When specifying the Suffix Mask, be sure to use the same cost code separator if the mask contains more than one segment.
Last Published Monday, August 28, 2023