Field Mappings Tab for OnePager Pro for Version 6.1
- 1 About the Project-View Properties form Field Mappings Tab
- 2 Field Mappings
- 3 Task/Milestone Identity Mapping
- 4 Field Splitting
- 5 Related Links
About the Project-View Properties form Field Mappings Tab
1) To compliment the Unlimited Field Mapping feature, we've changed the Other Columns tab on the Template Properties and added the a tab to the Project-View Properties forms.
- a) Previously, the Other Columns tab was only present on the Template Properties form. However, with the new Unlimited Column Mapping feature, it is appropriate for this tab to be present on the Project-View Properties form.
- b) For more information on the Unlimited Column Mapping feature, please consult the following link: Unlimited Field Mapping.
2) The name of the new tab is the Field Mappings tab.
- a) Since the Unlimited Field Mapping feature allows you to access all fields from Microsoft Project source plans at any time in the life cycle of a project view, the Field Mappings tab no longer needs to map fields to ‘extra purposes’ that are just carried along in case you need them.
- b) It now focuses on common OnePager purposes that users can map to Microsoft Project fields after a project view is created. Note, however, that other important OnePager purposes are on Rows/Swimlanes, Task Bars and Milestones tabs. And some purposes (e.g. Task Name, Percent-Complete, and Critical Path) appear both here and on the Task Bars and Milestones tabs
- c) For OnePager Pro there are eight (8) purposes named in the Field Mappings tab list below:
- (1) Percent-complete
- (2) Critical-path
- (3) Task-name
- (4) Start date
- (5) Finish date
- (6) Baseline start date
- (7) Baseline finish date
- (8) Deadline date
3) The Field Mappings tab for the PVP is shown below:
4) For OnePager Pro, the Unlimited Field Mapping includes Enterprise Custom Fields (ECF). Care should be taken, however, that you have turned on the ECF function in the current Template Properties form and established your connection to your project server service before creating the project view in the first place.
5) As in the Other Columns tab in previous versions, version 6.1 supports Field Splitting with the control on the Field Mappings tab in the Template form and Project-View Properties forms. Field Splitting can be performed on any source plan string type field with comma-separated components imported defined before the project view is created. It cannot be changed once a project view exists, though its value is shown in the Project-View Properties form to remind you of the splitting that is active in the project view.
6) Finally, we’ve added a group to the Field Mappings tab that shows the Microsoft Project field currently being used for the Task/Milestone Identity Mapping feature.
- a) In the PVP form, the Task/Milestone Identity Mapping is disabled but tells you which Microsoft Project field is being used.
- b) The Task/Milestone Identity Mapping field being used is specified in the Template Properties form to act as an alternate Unique ID field for OnePager Pro UPDATE operations. You can change it to whatever field you want, but it is your responsibility to make sure that the chosen field has a unique value for each task you plan to import and display in OnePager. Having duplicate values in the Unique ID field causes tasks to be omitted and/or misidentified later on when you are doing updates of the project view.
1) There are three (3) Basic Mappings in this group that are available to be remapped. You can use any Microsoft Project field of the appropriate type, and these are revealed in the individual dropdown menus as shown in the example below:
2) Selecting a different Microsoft Project field from the dropdown list tells OnePager to go back to the Microsoft Project source plan, retrieve the data for that field, and use that data for the purpose of the project view. This re-acquisition of Microsoft Project source plan data is done when you click Apply on the PVP form which keeps the PVP form visible or when you click OK which closes the PVP form. The project view is updated accordingly.
3) There are five (5) Date Mappings purposes in this group that are available to be remapped. You can use any Microsoft Project date field that can be revealed in the individual dropdown menus as shown in the example below:
4) As with the selections in the Basic Mappings group, selecting a different Microsoft Project field from the dropdown list tells OnePager to go back to the Microsoft Project source plan, retrieve the data for that field, and use that data for the designated the OnePager Pro purpose in the project view. This re-acquisition of Microsoft Project source plan data is done when you click Apply on the PVP form which keeps the PVP form visible or when you click OK which closes the PVP form. The project view is updated accordingly.
Task/Milestone Identity Mapping
Task/Milestone Identity Mapping for OnePager Pro Add-in and Desktop
1) In the Project-View Properties form, this group is for your information. The group is disabled but the Unique Id window shows the setting previously or currently set in the Template Properties form’s Field Mappings tab. As such, the window is for information purposes only and cannot be changed. The Task/Milestone Identity Mapping group is shown below:
2) The Unique Id field shows the Microsoft Project field that OnePager Pro used when it first created the project view.
3) This feature is added to assist advanced OnePager Pro users update project views that were created from sources where portions of one Microsoft Project source plan were copied into another.
- a) When OnePager updates a project view, it needs to identify each task and milestone that is being imported and find out if it already exists in project view. This is how OnePager preserves the formatting of the task/milestone and places it in the same row/swimlane where it resided before the update. When the data in the source plan is a .mpp file, OnePager has traditionally used the Microsoft Project Unique ID field for this purpose.
- b) However, you have no control over what values of Unique ID appear in the .mpp file when you copy data into that file. As a result, .mpp files that have had data copied into them can have problems preserving OPP's formatting and row/swimlane positioning.
- c) To solve this problem, version 6.1 lets you define and use a substitute MS Project field as an alternative Unique ID for uniquely identifying tasks. You are then responsible for guaranteeing that these field values are preserved when data is copied from one .mpp file to another. You are also responsible for making sure that there are no duplicate values in the field he designates for his alternative Unique ID usage.
- d) The alternate Unique ID can be set in one of two places:
- i) In the Template form's Field Mappings tab and
- ii) In the OnePager Choices form's second page by clicking the Edit current template... button.
- iii) We strongly recommend that you set the alternate Unique ID in the Template form rather than with the OPC form because this ensures that all project views use a consistent alternative Unique ID field
e:) Also you can consult this link for additional information: Advanced Tab for OnePager Pro - Reset Unique Ids On Update.
Task/Milestone Identity Mapping for OnePager Pro Using Source Plans from Microsoft Project Server and Microsoft Project Online
4) The discussion above focused on .mpp files as the Microsoft Project data source plans. The story is a little different if the source plan originates from a Microsoft Project Server or MS Project Online source.
- a) In these cases, there is no such thing as the Microsoft Project Unique ID field. In its place is a field that Microsoft calls the Global Unique ID or GUID field.
- b) And this GUID field is what OPP has traditionally used to identify tasks/milestone that it imports directly from MS Project Server/Online.
- c) Because people don't copy portions of server-based projects from one into another, the ability to define and use an alternative unique identifier is not as compelling as it is for .mpp files. But, you can still use the feature if you need special control over how tasks and milestones are identified from these server sources.
5) For additional help please go to the following link to the OnePager Frequently Asked Questions page: Selecting a Custom Unique ID.
1) As with the control group discussed previously, the Field Splitting group is disabled but shows the Microsoft Project field currently set in the Template Properties form as the field participating in field splitting. As such, the window is for information purposes only and cannot be changed. The Field Splitting group is shown below:
2) The Field Splitting control group in the Field Mappings tab of the OnePager Pro PVP form works in the same way as it did in the Other Columns tab of previous versions.
3) See the article at: Splitting and Parsing Columns-OnePager Pro for more information.