For performance reasons, OnePager imports a select set of fields from Microsoft Project or Excel. While users have always been able to use the template to control which fields are imported, OnePager had not previously given users a way to retroactively add a field to a project view, if it had not been imported originally. In OnePager 6.0, users can import any auxiliary field into an existing OnePager report, provided that there is only one snapshot. Here's an example:
- Go to Home > Project View Properties > Rows/Swimlanes. If you want to change your swimlane grouping, you would click on the swimlane dropdown. Notice that "Text30" is listed as an option, but "Text1" through "Text29" don't appear. This is because 1-29 were not initially imported when the project view was created:
- To retroactively import a field that wasn't included originally, scroll down to the bottom of your list of available fields until you get to the dashed line. Fields above this line have already been imported. Fields below the line exist in Project or Excel, but haven't been imported yet:
- In this example, we'll retroactively add "Text15" to our list of available columns. There is no magic required here. Simply select one of the unimported fields as your swimlane setting and click OK. OnePager will go back to your Project or Excel plan and bring in the data from the field you are adding.
- Once imported, the new field will appear above the dashed line for future use. Notice that both "Text15" and "Text30" are now above the dashed line as active fields:
Single Snapshot Requirement
For data integrity and performance reasons, retroactive field mappings are limited to project views that contain a single snapshot. This means that if you have a project view with multiple weekly or monthly snapshots, you will not be able to retroactively map a new auxiliary field until you reduce your project view to a single snapshot. To do this, go to View > List All. This will give you a list of all of your available snapshots. Highlight a snapshot and hit the Delete key on your keyboard until only one snapshot remains:
Once you have reduced your project view to only one snapshot, the dashed line will automatically appear in all of your dropdowns, indicating freedom to map new auxiliary fields.
The size of your OnePager project view (*.tam file) and OnePager's overall application performance is based on (1) the number of tasks that you have imported and (2) the number of fields you have imported for each task.
Addition of new tasks and new fields has a proportional effect on file size and on OnePager's import performance. For example, if you double the number of tasks and then double the number of fields, your *.tam file will increase 4x and it may take four times as long to update your data from Project or Excel. You should not see a performance impact to standard editing, such as conditional formatting, swimlanes, PDF export, or drag-and-drop editing.
With this in mind, we recommend only importing fields that you think you will actually use, as there is not currently a plan to let users un-import fields that are no longer required.