About Data Mapping templates
When a project in Unifier is linked to a project in P6, each project retain their respective name, with no changes applied to the names.
Establishing a link between a project in Unifier and a project in P6 is based on a specific Data Element (DE) in Unifier (uuu_int_p6_Project_id) corresponding to a specific P6 element (Project ID).
The following lists the out-of-the-box (OOTB) Data Mapping templates available for use and provides a description for each template.
Create Activity Sheet from P6
Use this template to map all the fields in the Activity Sheet to the P6 Activity object that is needed from P6. You can use this template to create a new Activity Sheet in Unifier projects.
There are 26 pre-defined elements that are included in the Activity Sheet Attribute form. By default, this template contains the first 24 pre-defined elements that are included in the Activity Sheet Attribute form, and the fields are mapped to the corresponding P6 Activity object.
The following elements are excluded from this template:
- Primary Constraint
- Secondary Constraint
You can deploy custom activity attributes to Gateway and then add those attributes to this template.
Update Activity Sheet from P6
Use this template to update an existing Activity Sheet in a Unifier project based on P6 data.
There are 26 pre-defined elements that are included in the Activity Sheet Attribute form. By default, this template contains 22 pre-defined elements that are included in the Activity Sheet Attribute form, which cannot be populated by Reverse Auto-Population. As a result, the template does not contain the following elements:
- Actual Start
- Actual Finish
- Primary Constraint
- Secondary Constraint
You can deploy custom activity attributes to Gateway and then add those attributes to this template.
Send Activity data to P6
Use this template to map those fields in the Activity Sheet Attribute form, to P6 Activity object, that might get updated in Unifier by way of a Business Process record. These fields need to be updated from Unifier to P6 through Gateway.
There are 26 pre-defined elements that are included in the Activity Sheet Attribute form. By default, this template contains the 2 fields that can be populated by Reverse Auto-Population. As a result, the template contain the following two elements, only:
- Actual Start
- Actual Finish
You can deploy custom activity attributes to Gateway and then add those attributes to this template.
Note: The fields in this template must be maintained exclusive of the fields in the "Update Activity Sheet from P6" template. There are no common fields between the "Send Activity Data to P6" template and the "Update Activity Sheet from P6" template. If you add the common fields to the two templates, inaccurate information can be generated in either application (Unifier or P6).
Editing Data Mapping templates
You can edit (take out a field or add a new field) any of the Data Mapping templates mentioned in this section by going to Gateway > Configuration > Customization.
- From the Customization window, select the "Activity" business object from the "Select Business Object’' drop-down list to see all Data Mappings, based on the "Activity" object.
- Select any Data Mapping template.
- Click Edit and go to the Mappings tab.
- Add a new field, to exchange data for example.
You can add any custom field to an Activity Sheet Attribute form in uDesigner and Deploy the Activity Sheet Attribute form to Gateway. All the fields from the Activity Sheet Attribute form appear in Unifier (P6 Activity Sheet drop-down list). As a result, you can select any Activity Sheet Attribute form that you have defined in Unifier and map the Activity Sheet Attribute form to a corresponding activity field (fixed field or user-defined field) in P6; however, ensure that you map the Unifier element to the Activity Sheet Attribute form in a way that the "Data Types" of the P6 Activity elements match the Data Definitions (DEs) of the Unifier Activity Sheet Attribute form. The following shows the mapping of data between the P6 Data Types and the corresponding Unifier DEs.
P6 Data Type | Corresponding Unifier Data Definition |
|---|---|
Text (40 chars) | SYS Short Description Text 50 |
Text (120 chars) | SYS Short Description Text 120 |
Text (UDF* Fields) | SYS Short Description Text 255 |
Date | Date Picker |
Cost | Currency Amount |
Number | Decimal Amount |
Integer | Integer Amount |
Indicator | SYS P6 Indicator Note: In the Edit window of the Data Mapping template, Gateway does not display "Indicator," as an available field type. As a reasult, you need to map an "Indicator" type field from Unifier to P6 UDF and set the "Data Type" as "String." |
Activity Status Pulldown | SYS Short Description Text 50 |
Activity Type Pulldown | SYS Short Description Text 50 |
*UDF: User-defined Field
Additional information about editing Data Mapping templates
In P6 some activity attributes fields, cannot be updated manually, or by way of any other methods. These fields must be calculated using the P6 internal logic. If you modify the "Send Activity Data to P6" Data Mapping template to map to a P6 activity attributes field that cannot be updated, then:
- The P6 internal logic prevents the mapping during integration and synchronization will fail.
- The data in P6 is updated incorrectly.
Ensure that you are aware of the limitations when you add a new field to the "Send Activity Data to P6" Data Mapping template.
Since the "Actual Finish" field is added to the "Send Activity Data to P6" Data Mapping template and based on the value of the "Activity Type" field in P6, the "Actual Finish" field gets calculated, in P6, you must not keep the "Actual Finish" field in the "Send Activity Data to P6" Data Mapping template. Instead, you must keep the "Actual Finish" field in the "Update Activity Sheet from P6' Data Mapping template.
In short, you need to keep, or designate, only one application (Unifier or P6) as the source for each field. This is to prevent a field to get updated in both applications (Unifier or P6).