Difference between pages "Automatically Cropping Empty Rows for OnePager Express for Version 6.1" and "OnePager Express Import of Data from Microsoft Excel for Version 7.2"

From OnePager Documentation
(Difference between pages)
Jump to: navigation, search
 
 
Line 1: Line 1:
==Overview==
+
==About Importing Microsoft Excel Data to OnePager Express==
  
1) When you are moving task/milestone to different rows and swimlanes, you can end up with '''unoccupied rows''' that you can '''hide''' if necessary.  
+
Illustrations used in this article are from OnePager Express but the feature's function, controls, and manual edits apply equally to OnePager Bundle when the '''source plan imported''' into OnePager Bundle is Microsoft Excel.
  
2) OnePager has a convenient feature to do this quickly and easily: '''auto-hiding'''.  
+
OnePager Express ('''OPX''') imports data from your Microsoft Excel '''source plan''' and allows you to select which of the Microsoft Excel '''source plan fields''' to process and how they are to be processed through the OnePager choices ('''OPC''') form. Since Microsoft Excel is so flexible, OnePager is constructed with significant intelligence to determine how you want to represent the imported data.  This built in intelligence is applied in two ways:
  
3) To use this feature, click the '''Hide''' button on the OnePager ribbon as shown below:  
+
:1) OnePager scans all your Microsoft Excel '''source plan fields''' and looks for '''field headers''' that can be useful for the creation of a chart.  Once this analysis is complete, '''OPX''' populates the second page of the '''OPC''' form with its findings as shown below:
  
<center>[[File:X61-12_15_1-61-(1)-11302018.png]]</center>
+
<center>[[File:X61-4_0_1_4-61-(1)-10252017.png]]</center>
<!--center><X61-12_15_1-61-(1)-11302018.png></center-->
+
<!--<center>X61-4_0_1_4-61-(1)-10252017.png</center>-->
  
4) Clicking the '''Home''' tab's '''Hide''' button accesses the '''Row hiding choices''' form shown here:
+
:2) '''OPX''' recognizes information in the various Microsoft Excel '''source plan fields''' after finding and analyzing the '''field headers''' and after examining the type of data in each '''field'''.
  
<center>[[File:X61-12_15_1-61-(2)-11302018.png]]</center>
+
'''OPX''' intelligently makes changes to the current '''Template Properties''' form's settings to reflect these findings and reports them to you in the '''OPC''' form shown above.
<!--center><X61-12_15_1-61-(2)-11302018.png></center-->
+
  
5) The '''Row hiding choices''' form shown above shows that one (1) '''Interior''' row is empty and can be '''hidden'''.  The project view with the '''empty row''' looks like this with the '''Row hiding choices''' form shown:
+
==Data Import to OnePager Express==
  
<center>[[File:X61-12_15_1-61-(3)-11302018.png]]</center>
+
What follows is a discussion of how OnePager Express applies it’s built in intelligence functions for you. Our goal here is to provide sufficient understanding of the process so you know what to expect from OnePager Express when various '''field heading''' names and data types are encountered by OnePager Express from your Microsoft Excel '''source plan'''. There are four data types that '''OPX''' looks for when importing data from Microsoft Excel:
<!--center><X61-12_15_1-61-(3)-11302018.png></center-->
+
  
Clicking the '''OK''' button on the form '''hides''' the empty row as discussed in the following sections.
+
:* Dates
 +
:* Numbers
 +
:* Boolean (TRUE or FALSE)
 +
:* Strings (A through Z, 0-9, special characters)
  
==Auto Hiding Options==
+
All data, regardless of data type, are imported from Microsoft Excel.  '''OPX''' begins this analysis from top-left to bottom-right. '''OPX''' ignores merged cells in fields and merged cells in rows. Once the '''field headers''' are located and the data types are analyzed, '''OPX''' associates these '''fields''' with specific usages in the '''OPC''' form as illustrated above. Using the second page of the '''OPC''' form shown above, you can change the '''field''' usage by selecting another '''field''' to serve the function from the dropdown list provided.  The dropdown list is built from all the '''field headers''' that '''OPX''' found during its analysis pass.  An example of a dropdown list of '''field header''' names taken from a Microsoft Excel '''source plan''' is shown here:
  
===Using the Home Tab Hide Rows Button on the OnePager Ribbon===
+
<center>[[File:X61-4_0_1_4-61-(2)-10252017.png]]</center>
 +
<!--<center>X61-4_0_1_4-61-(2)-10252017.png</center>-->
  
1) As demonstrated in the previous section clicking the '''Hide''' button accesses the '''Row hiding choices''' form.  
+
When the '''Create new Chart''' button is clicked, OnePager uses your '''field''' assignments to create the chart.
  
2) Use the checkboxes on the form to specify where you want OnePager to automatically '''hide rows''' and click '''OK''' as shown in the last illustration in the previous section.
+
==Intelligent Changes Made to OnePager Express Current Template Properties Forms==
  
3) Clicking the '''OK''' button '''hides''' the indicated row(s) as shown here:
+
'''OPX''' is shipped to you with a predefined set of '''Template Properties''' forms that are based upon the '''BlueGrass Project Plan Report - Express''' used in this Wiki for example purposes and available to you from the '''OPX''' tutorial.  This means that all '''field''' usage settings within these shipped '''Template Properties''' forms are based upon this Microsoft Excel '''source plan'''. Since the flexibility of Microsoft Excel needed to be considered in the design of '''OPX''', it was necessary to '''update''' the current '''Template Properties''' form based upon '''your''' Microsoft Excel '''source plan'''. Accordingly, '''OPX''' uses the analysis techniques discussed above to modify the '''current Template Properties''' form.  This is necessary because, unlike Microsoft Project, where the '''fields''' have predefined meanings, the Microsoft Excel '''source plan field''' assignments and meaning are totally determined by you.  '''OPX''', therefore, makes intelligent recommendations on Microsoft Excel '''source plan field''' usage based on the findings of the intelligent engine. 
  
<center>[[File:X61-12_15_1-61-(4)-11302018.png]]</center>
+
You can change or override these findings as follows:  
<!--center><X61-12_15_1-61-(4)-11302018.png></center-->
+
  
===Using the Template/PVP Advance Tab's Row Hiding Options Button===
+
:1) You can click the '''Edit current Template…''' button also on the second page of the OnePager choices ('''OPC''') form shown above. 
  
4) OnePager offers you a set of controls by which you can '''govern''' how '''automatic hiding''' functions are performed.   
+
:2) Clicking this button brings up the '''Template Properties''' form at the '''Rows and Swimlanes''' tab.
 +
 +
:3) The settings found in the '''Row & Swimlanes''' tab are determined by the '''current Template Properties''' form and by the intelligent analysis described above.  
 +
   
 +
:4) If your Microsoft Excel '''source plan''' contains a '''field heading''' that exists in the '''Template Properties''' form, OnePager uses that '''fields'''. 
  
5) These controls are found both in the '''Template Properties''' and the Project-View Properties ('''PVP''') forms at their respective '''Advanced''' tabs at the '''Row hiding options''' button shown below:
+
Otherwise, it makes an intelligent recommendation from the '''field headings''' it discovers.  The figure below shows that several of the settings in the '''Template Properties''' form’s '''Rows & Swimlanes''' tab reflect the decisions that OnePager made concerning '''field''' usage.  These settings are consistent with the selections displayed in the '''OPC''' form.
  
<center>[[File:X61-12_15_1-61-(5)-11302018.png]]</center>
+
<center>[[File:X71-4_0_1_4-71-(3-1)-02182022.png]]</center>
<!--center><X61-12_15_1-61-(5)-11302018.png></center-->
+
<!--<center>X71-4_0_1_4-71-(3-1)-02182022.png</center>-->
  
6) These controls have the following effects:
+
'''Note''' in the highlighted rectangles above, that '''OPC''' picked up the '''Task Name''' '''field''' for collecting tasks into rows. To access the form for selecting '''text column''' names, click the '''Text Column Properties...''' button to access the '''Custom Text Column''' form as shown above. The illustration above shows that the '''“Lemgth”''' '''field''' from the Microsoft Excel '''source plan''' is selected as the '''text column''' to appear in the chart. The '''“Lemgth”''' '''field''' is indicated in the '''Template''' form's '''Rows/Swimlanes''' tab for ordering rows.  We purposely misspelled '''Length''' to illustrate that '''OPX''' has the intelligence to pick '''fields''' even though their headings are somewhat misspelled. You can change the rows and swimlane settings as well as settings in any of the other tabs.  When you are ready, click '''Save and use''' button to make these changes part of the '''current Template Properties''' form.
  
:a) '''Look at current snapshot only'''.  When this checkbox is checked '''ON''', OnePager looks only at the '''current snapshot''' to determine which rows are empty. When this checkbox is not checked or in the '''OFF''' setting, OnePager looks at '''all snapshots''' before deciding that a row is empty.  In either case, please note that any rows that are hidden are hidden in '''all snapshots'''.
+
In other tabs of the '''Template Properties''' form, '''OPX''' has adjusted settings in a similar way to be consistent with its intelligent engine’s analysis of the Microsoft Excel '''source plan field headers''' and data types. If '''OPX''' cannot find a '''field header''' name in the Microsoft Excel '''source plan''' that can be correlated with a specific '''OPX''' purpose, '''OPX''' makes as intelligent a guess as possible and you are then able to make any change necessary. You are '''cautioned''' that all '''current Template Properties''' forms are altered when used in this way.  We recommend that unique '''Template Properties''' form names be subsequently given to such modified '''Template Properties''' form for future reference and for sharing these modified '''Template Properties''' form with others.
  
:b) '''Hide newly-empty rows on import'''.  When this checkbox is checked '''ON''', OnePager '''automatically hides''' any rows that become empty when you '''add or update a snapshot'''.    This can happen when a task or milestone is present at some '''snapshots''' but is missing from the '''snapshot''' that you are currently updating.    Bear in mind, however, that the hidden rows are now being '''hidden''' in '''all snapshots''' and not just in the '''snapshot''' you are updating.
+
==Missing Fields, Field Headers, or Misspelled Field Headings==
  
:c) '''Unhide rows for flagged tasks/milestones'''.  When this checkbox is checked '''ON''', OnePager '''automatically unhides''' tasks/milestones, rows, and swimlanes that were '''hidden''' in previous '''snapshots''' if any of the tasks/milestones are '''flagged''' for import on the '''current snapshot'''.  This assures that in '''new snapshots''' you see all previously '''hidden''' tasks/milestones and their previously '''hidden''' rows and swimlanes.  If the checkbox is not checked or '''OFF''', OnePager continues to '''hide''' previously '''hidden''' rows and swimlanes as the '''new snapshot''' is created.  The default setting for this feature is with the checkbox '''checked ON'''.
+
'''OPX''' also checks '''field headings''' when importing data in '''UPDATE''' mode.  If the '''field''' was used in previous '''snapshots''' for any purpose, OnePager checks to assure that the new import for the '''snapshot''' has those same '''fields'''.  When '''OPX''' cannot find the expected '''fields''', one or more '''field heading''' names are missing or blank, the '''field heading''' is recognizably misspelled, or the data type is different from the previous snapshot, '''OPX''' provides a '''warning message''' as shown in the example below:
  
:d) '''Hide rows when dates are outside the date range'''.  When this option is checked '''ON''', clicking the '''Hide''' button '''hides''' rows that appear empty because the task/milestones occupying those rows are outside the '''start-end dates''' for the project view (See [[Advanced Tab for OnePager Express for Version 6.1 | Advanced Tab-OnePager Express]] <!--21.14.1-61-->). When this option is checked '''ON''', OnePager knows that you want rows where tasks/milestones are not within the '''start-end dates''' range of the project view to be '''hidden''' when you click the '''Hide''' button on the ribbon.
+
<center>[[File:X52-4_4-(4)-06082015.png]]</center>
 +
<!--<center>X52-4_4-(4)-06082015.png</center>-->
  
5) As with the '''Look at current snapshot only''' row '''hiding''' action, the row '''hiding''' does not occur until you click the '''Hide''' button on the '''Home''' ribbon tab.
+
This can occur when you inadvertently attempt to update a chart from the incorrect Microsoft Excel '''source plan''' or the desired Microsoft Excel '''source plan''' was altered to the extent that '''OPX''' cannot find the '''fields''' needed to accomplish the '''UPDATE''' functions. You are given two choices when the message above is displayed:
  
==Finding Hidden Rows==
+
===Select Yes===
  
1) If rows are '''hidden''', for any reason, they can be found by using the '''Where’s My Stuff?!''' feature accessed from the '''Show/Hide''' button on the '''Home''' ribbon.
+
By selecting the '''Yes''' button, the import proceeds.  OnePager blanks some values that it cannot find. '''Note:''' The results can be unexpected.
  
2) An example of a “Where’s My Stuff?!” form where out of range rows are '''hidden''' is shown below:
+
===Select No===
  
<center>[[File:X61-12_15_1-61-(6)-11302018.png]]</center>
+
Selecting the '''No''' button tells '''OPX''' to stop the import process and return control to Microsoft Excel. You can now correct the Microsoft Excel '''source plan''' or select another one and start the '''UPDATE''' process again.
<!--center><X61-12_15_1-61-(6)-11302018.png></center-->
+
 
+
3) For more information on the use of the '''Where's My Stuff?!''' feature and form, please see the article at:  [[Managing Hidden Tasks and Milestones Using "Where's My Stuff?!" for Version 6.1 | Managing Hidden Tasks and Milestones Using "Where's My Stuff?!"]]. <!--9.4.1-61.-->
+
  
 
==Related Links==
 
==Related Links==
  
[[Advanced Tab for OnePager Express for Version 6.1 | Advanced Tab-OnePager Express]] <!--21.14.1-61-->
+
[[Basic Workflows for Version 7.2 (Portal) | Basic Workflows (Portal)]] 7.0.1-72
 +
 
 +
[[Merging the Wrong Tasks into a Chart for Version 7.2 - OnePager Express | Merging the Wrong Tasks into a Chart - OnePager Express]] 7.12.1-72
  
[[Managing Hidden Tasks and Milestones Using "Where's My Stuff?!" for Version 6.1 | Managing Hidden Tasks and Milestones Using "Where's My Stuff?!"]] <!--9.4.1-61-->
+
[[Data-Driven Task Links for OnePager for Version 7.2 | Data-Driven Task Links for OnePager Pro and Express]] 19.1.1.1-72
  
(12.15.1-61)
+
(4.0.1.4-72)
  
[[Category:Version 6.1]]
+
[[Category:Version 7.2]]
[[Category:Project Views]]
+
[[Category:Getting Started with Version 7.2]]
 +
[[Category:Core Concepts]]
 +
[[Category:OnePager Choices Form]]
 
[[Category:Templates]]
 
[[Category:Templates]]
[[Category:Project-View Properties Form]]
+
[[Category:Task Links]]
[[Category:Editing a Project View]]
+
[[Category:Text Columns]]
[[Category:OnePager - Tool Bar]]
+
 
[[Category:Rows and Swimlanes]]
 
[[Category:Rows and Swimlanes]]
[[Category:Rows]]
+
[[Category:Multiple Swimlane Levels]]
[[Category:Hiding Rows]]
+
[[Category:Importing]]
[[Category:Mavericks]]
+
[[Category:Charts]]
 +
[[Category:Templates Versus Charts]]
 +
[[Category:Importing]]
 +
[[Category:Microsoft Excel]]
 
[[Category:OnePager Express]]
 
[[Category:OnePager Express]]
 +
[[Category:OnePager Bundle]]

Revision as of 14:40, 31 May 2022

About Importing Microsoft Excel Data to OnePager Express

Illustrations used in this article are from OnePager Express but the feature's function, controls, and manual edits apply equally to OnePager Bundle when the source plan imported into OnePager Bundle is Microsoft Excel.

OnePager Express (OPX) imports data from your Microsoft Excel source plan and allows you to select which of the Microsoft Excel source plan fields to process and how they are to be processed through the OnePager choices (OPC) form. Since Microsoft Excel is so flexible, OnePager is constructed with significant intelligence to determine how you want to represent the imported data. This built in intelligence is applied in two ways:

1) OnePager scans all your Microsoft Excel source plan fields and looks for field headers that can be useful for the creation of a chart. Once this analysis is complete, OPX populates the second page of the OPC form with its findings as shown below:
X61-4 0 1 4-61-(1)-10252017.png
2) OPX recognizes information in the various Microsoft Excel source plan fields after finding and analyzing the field headers and after examining the type of data in each field.

OPX intelligently makes changes to the current Template Properties form's settings to reflect these findings and reports them to you in the OPC form shown above.

Data Import to OnePager Express

What follows is a discussion of how OnePager Express applies it’s built in intelligence functions for you. Our goal here is to provide sufficient understanding of the process so you know what to expect from OnePager Express when various field heading names and data types are encountered by OnePager Express from your Microsoft Excel source plan. There are four data types that OPX looks for when importing data from Microsoft Excel:

  • Dates
  • Numbers
  • Boolean (TRUE or FALSE)
  • Strings (A through Z, 0-9, special characters)

All data, regardless of data type, are imported from Microsoft Excel. OPX begins this analysis from top-left to bottom-right. OPX ignores merged cells in fields and merged cells in rows. Once the field headers are located and the data types are analyzed, OPX associates these fields with specific usages in the OPC form as illustrated above. Using the second page of the OPC form shown above, you can change the field usage by selecting another field to serve the function from the dropdown list provided. The dropdown list is built from all the field headers that OPX found during its analysis pass. An example of a dropdown list of field header names taken from a Microsoft Excel source plan is shown here:

X61-4 0 1 4-61-(2)-10252017.png

When the Create new Chart button is clicked, OnePager uses your field assignments to create the chart.

Intelligent Changes Made to OnePager Express Current Template Properties Forms

OPX is shipped to you with a predefined set of Template Properties forms that are based upon the BlueGrass Project Plan Report - Express used in this Wiki for example purposes and available to you from the OPX tutorial. This means that all field usage settings within these shipped Template Properties forms are based upon this Microsoft Excel source plan. Since the flexibility of Microsoft Excel needed to be considered in the design of OPX, it was necessary to update the current Template Properties form based upon your Microsoft Excel source plan. Accordingly, OPX uses the analysis techniques discussed above to modify the current Template Properties form. This is necessary because, unlike Microsoft Project, where the fields have predefined meanings, the Microsoft Excel source plan field assignments and meaning are totally determined by you. OPX, therefore, makes intelligent recommendations on Microsoft Excel source plan field usage based on the findings of the intelligent engine.

You can change or override these findings as follows:

1) You can click the Edit current Template… button also on the second page of the OnePager choices (OPC) form shown above.
2) Clicking this button brings up the Template Properties form at the Rows and Swimlanes tab.
3) The settings found in the Row & Swimlanes tab are determined by the current Template Properties form and by the intelligent analysis described above.
4) If your Microsoft Excel source plan contains a field heading that exists in the Template Properties form, OnePager uses that fields.

Otherwise, it makes an intelligent recommendation from the field headings it discovers. The figure below shows that several of the settings in the Template Properties form’s Rows & Swimlanes tab reflect the decisions that OnePager made concerning field usage. These settings are consistent with the selections displayed in the OPC form.

X71-4 0 1 4-71-(3-1)-02182022.png

Note in the highlighted rectangles above, that OPC picked up the Task Name field for collecting tasks into rows. To access the form for selecting text column names, click the Text Column Properties... button to access the Custom Text Column form as shown above. The illustration above shows that the “Lemgth” field from the Microsoft Excel source plan is selected as the text column to appear in the chart. The “Lemgth” field is indicated in the Template form's Rows/Swimlanes tab for ordering rows. We purposely misspelled Length to illustrate that OPX has the intelligence to pick fields even though their headings are somewhat misspelled. You can change the rows and swimlane settings as well as settings in any of the other tabs. When you are ready, click Save and use button to make these changes part of the current Template Properties form.

In other tabs of the Template Properties form, OPX has adjusted settings in a similar way to be consistent with its intelligent engine’s analysis of the Microsoft Excel source plan field headers and data types. If OPX cannot find a field header name in the Microsoft Excel source plan that can be correlated with a specific OPX purpose, OPX makes as intelligent a guess as possible and you are then able to make any change necessary. You are cautioned that all current Template Properties forms are altered when used in this way. We recommend that unique Template Properties form names be subsequently given to such modified Template Properties form for future reference and for sharing these modified Template Properties form with others.

Missing Fields, Field Headers, or Misspelled Field Headings

OPX also checks field headings when importing data in UPDATE mode. If the field was used in previous snapshots for any purpose, OnePager checks to assure that the new import for the snapshot has those same fields. When OPX cannot find the expected fields, one or more field heading names are missing or blank, the field heading is recognizably misspelled, or the data type is different from the previous snapshot, OPX provides a warning message as shown in the example below:

X52-4 4-(4)-06082015.png

This can occur when you inadvertently attempt to update a chart from the incorrect Microsoft Excel source plan or the desired Microsoft Excel source plan was altered to the extent that OPX cannot find the fields needed to accomplish the UPDATE functions. You are given two choices when the message above is displayed:

Select Yes

By selecting the Yes button, the import proceeds. OnePager blanks some values that it cannot find. Note: The results can be unexpected.

Select No

Selecting the No button tells OPX to stop the import process and return control to Microsoft Excel. You can now correct the Microsoft Excel source plan or select another one and start the UPDATE process again.

Related Links

Basic Workflows (Portal) 7.0.1-72

Merging the Wrong Tasks into a Chart - OnePager Express 7.12.1-72

Data-Driven Task Links for OnePager Pro and Express 19.1.1.1-72

(4.0.1.4-72)