Revision as of 14:51, 12 May 2017

About the Project-View Properties form Field Mappings Tab

Overview

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, the Field Mappings tab is a significantly simplified tab.

b) It now focuses on those Microsoft Project fields that customers tell us are the most frequent fields they wish to remap into other OnePager columns after a project view is created.

c) For OnePager Pro there are eight (8) Microsoft Project fields as 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 first project view.

5) As in the Other Columns tab in previous versions, version 6.0 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 either before or after the project view is created.

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 feature.

a) In the PVP form, the Task/Milestone Identity is ghosted but tells you which Microsoft Project field is being used.

b) The Task/Milestone Identity field being used is specified in the Template Properties form to act as an alternate Unique ID field for OnePager Pro UPDATE operations.

Field Mappings

Basic Fields

1) There are three (3) Basic Fields in this group that are available to be remapped. You may use any Microsoft Project field of the same 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 to populate the associated OnePager Pro columns however they may be used in the project view. This re-acquisition of Microsoft Project source plan data is done immediately and the project view is updated accordingly regardless of the mode of operation (i.e., NEW, UPDATE or OPEN).

Date Fields

1) There are five (5) Date Fields in this group that are available to be remapped. You may use any Microsoft Project date field that can be revealed in the individual dropdown menus as shown in the example below:

2) As with the selections in the Basic Fields 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 to populate the OnePager Pro column however it may be used in the project view. This reacquisition of Microsoft Project source plan data is done immediately and the project view is updated accordingly regardless of the mode of operation (i.e., UPDATE or OPEN).

Task/Milestone Identity

1) In the Project-View Properties form, this group is for your information. The group is ghosted 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 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 who create project views from multiple Microsoft Project source plans or who find it necessary to copy portions of one Microsoft Project source plan into another for updating project views.

a) See the section in the article at this link: Advanced Tab for OnePager Pro-Reset Unique Ids On Update .

b) This section of the linked article provides guidance on using this feature to reset the Unique ID field so that OnePager Pro can properly perform project view update in the future.

Field Splitting

1) As with the control group discussed previously, the Field Splitting group is ghosted 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.

Related Links

Unlimited Field Mapping

Advanced Tab for OnePager Pro-Reset unique ids on update

Splitting and Parsing Columns-OnePager Pro

(21.15.1-60)