Difference between revisions of "Conditional Import for OnePager Pro/Express Version 6.0"

From OnePager Documentation
Jump to: navigation, search
(Related Links:)
(Using Text Fields with Conditional Import Filters)
 
(37 intermediate revisions by the same user not shown)
Line 1: Line 1:
===About Conditional Import for OnePager (PE60-0_4_1_1-11112016)===
+
===About Conditional Import Filters for OnePager===
  
In '''OPP''' and '''OPX''' version 6.0, the capability for you to control the '''import''' of rows from your source plan is made even more flexible with the addition of new '''Conditional Import''' capabilities. Here we overview some situations you may have encountered in the past with OnePager that can be facilitated better with '''Conditional Import'''.
+
In '''OPP''' and '''OPX''' version 6.0, the capability for you to control the '''import''' of rows from your '''source plan''' is made even more flexible with the new '''Conditional Import Filters''' capabilities. Here we overview some situations you may have encountered in the past with OnePager that can be facilitated better with '''Conditional Import Filters'''.
  
 
===When a Flag Field Isn’t Sufficient===
 
===When a Flag Field Isn’t Sufficient===
  
1) There are occasions where you would like to '''import '''a source plan row but only when the contents of a specified column holds a desired value or range of values for that row. In this case, using a flag field may not be flexible enough or may be too time consuming to use.
+
1) There are occasions where you would like to '''import''' a '''source plan''' row but only when the contents of a specified '''field''' holds a desired value or range of values. In this case, using a '''flag''' field may not be flexible enough or may be too time consuming.
  
2) Suppose you want to include source plan rows where task/milestone '''Start''' dates are greater than a specified date. Prior to OnePager version 6.0 you would have to manually locate and modify the '''flag''' cell contents for those rows meeting the desired condition before importing data to OnePager.  With version 6.0 you can clearly specify, in a '''Conditional Import''' rule, defined before the import process begins, the conditions that meet any logical combination of criteria '''WITHOUT''' making modifications to the source plan. Here’s how it might work:
+
2) Suppose you want to include '''source plan''' rows where task/milestone '''Start''' dates are greater than a specified date.  With version 6.0 you can specify, in a '''Conditional Import Filters''' rule, the conditions that meet any logical combination of criteria. Here’s how it works:
  
:a) We’ll use the BlueGrass Project 2J-303 Microsoft Project source plan as an example.  Recall that  the column headers look something like this:
+
:a) We’ll use the BlueGrass Project 2J-303 Microsoft Project '''source plan''' as an example.  Recall that  the '''field''' headers look something like this:
  
 
<center>[[File:P60-7_18_1-60-(1)-09242016.png]]</center>
 
<center>[[File:P60-7_18_1-60-(1)-09242016.png]]</center>
<center>P60-7_18_1-60-(1)-09242016.png</center>
+
<!--<center>P60-7_18_1-60-(1)-09242016.png</center>--
  
:b) For this example you only want to import tasks/milestones that have a '''Start''' date greater than 10/11/2015 but less than 12/31/2015.  You can do this by first launching Microsoft Project with the source plan loaded as shown above.  Next, launch '''OPP''' version 6.0 from the Microsoft Project tool bar as you normally do and click the '''NEW''' button option.  When this is done the following '''OnePager Choices ''' form appears:
+
:b) For this example you only want to import tasks/milestones that have a '''Start''' date greater than 10/11/2015 but less than 12/31/2015.  First launch Microsoft Project with the '''source plan''' loaded as shown above.  Next, launch '''OPP''' version 6.0 from the Microsoft Project tool bar and click the '''NEW''' button option.  When this is done the following '''OnePager Choices''' form appears:
  
 
<center>[[File:P60-7_18_1-60-(2A)-12272016.png]]</center>
 
<center>[[File:P60-7_18_1-60-(2A)-12272016.png]]</center>
<center>P60-7_18_1-60-(2A)-12272016.png</center>
+
<!--<center>P60-7_18_1-60-(2A)-12272016.png</center>-->
  
:c) The '''OnePager choices''' ('''OPC''') form above has an additional radio button in the '''Task Selection''' group, '''Select tasks by custom filter''' and a new button called '''Edit filter…'''.  Before clicking the '''Select tasks by customer filter''' button, update the project view name and snapshot date such that the '''OPC''' form looks like this:
+
:c) The OnePager choices ('''OPC''') form below has an additional radio button in the '''Task Selection''' group, '''Select tasks by custom filter''', and a new button called '''Edit filter…'''.  Before clicking the '''Select tasks by customer filter''' button, the '''OPC''' form looks like this:
  
 
<center>[[File:P60-7_18_1-60-(3A)-12272016.png]]</center>
 
<center>[[File:P60-7_18_1-60-(3A)-12272016.png]]</center>
<center>P60-7_18_1-60-(3A)-12272016.png</center>
+
<!--<center>P60-7_18_1-60-(3A)-12272016.png</center>-->
  
 
:d) Now, click the '''Select tasks by custom filter''' button.  When you do, a blank '''Custom Import Rules''' form will appear as show below:
 
:d) Now, click the '''Select tasks by custom filter''' button.  When you do, a blank '''Custom Import Rules''' form will appear as show below:
  
<center>[[File:P60-7_18_1-60-(4A)-12272016.png]]</center>
+
<center>[[File:P60-7_18_1-60-(4BB)-03022017.png]]</center>
<center>P60-7_18_1-60-(4A)-12272016.png</center>
+
<!--<center>P60-7_18_1-60-(4BB)-03022017.png</center>-->
  
 
:e) You can now compose the two rules needed to import rows that have '''Start''' dates greater than 10/11/2015 but less than 12/31/2015.  When you do this, the '''Conditional Import Rules''' form will look like this:
 
:e) You can now compose the two rules needed to import rows that have '''Start''' dates greater than 10/11/2015 but less than 12/31/2015.  When you do this, the '''Conditional Import Rules''' form will look like this:
  
<center>[[File:P60-7_18_1-60-(5A)-12272016.png]]</center>
+
<center>[[File:P60-7_18_1-60-(5BB)-03022017.png]]</center>
<center>P60-7_18_1-60-(5A)-12272016.png</center>
+
<!--<center>P60-7_18_1-60-(5BB)-03022017.png</center>-->
  
:f) Note that the '''All of the following rules are true''' radio button is selected so that the two rules are essentially an '''AND''' operation.  When you click '''OK''' on the form, it will disappear and you will be back at the '''OPC''' form once more.  At this point. click the '''Create new project view''' button and '''OPP''' will create the project view that looks like this:
+
:f) Note that the '''All of the following rules are true''' radio button is selected so that the two rules are essentially an '''AND''' operation.  When you click '''OK''' on the form, this form will disappear and you will be back at the '''OPC''' form once more.  Now, click the '''Create new project view''' button and '''OPP''' will create the project view that looks like this:
  
 
<center>[[File:P60-7_18_1-60-(6)-09242016.png]]</center>
 
<center>[[File:P60-7_18_1-60-(6)-09242016.png]]</center>
<center>P60-7_18_1-60-(6)-09242016.png</center>
+
<!--<center>P60-7_18_1-60-(6)-09242016.png</center>-->
  
 
:g) In the project view above, there are tasks that extend beyond 12/31/2015 but there are no tasks that '''Start''' on or after 12/31/2015.  Similarly, there are no tasks that '''Start''' before 10/11/2015.
 
:g) In the project view above, there are tasks that extend beyond 12/31/2015 but there are no tasks that '''Start''' on or after 12/31/2015.  Similarly, there are no tasks that '''Start''' before 10/11/2015.
  
:h) When the project view is saved, the '''Conditional Import''' rules are saved as well and will be used to control the '''import''' for subsequent snapshots.  Further, in either this snapshot or subsequent ones, the '''Conditional Import''' rules can be edited (i.e., changed, added, or deleted).  When such changes are made to the '''Conditional Import''' rules, the current '''new snapshot''' or the '''snapshot''' being '''replaced '''will be configured by the active set of '''Conditional Import''' rules.  Finally, you can always revert to using '''flag''' columns or select '''All''' tasks for import.
+
:h) When the project view is saved, the '''Conditional Import Filters''' rules are saved as well and will be used to control the '''import''' for subsequent snapshots.  Further, the '''Conditional Import Filters''' rules can be edited (i.e., changed, added, or deleted).  When such changes are made to the '''Conditional Import Filters''' rules, any '''new snapshot''' or '''snapshot''' being '''replaced '''will be configured by the active set of '''Conditional Import Filters''' rules.  Finally, you can always revert to using '''flag''' fields or select '''All''' tasks for import.
  
:i) An important thing to remember is that the '''Conditional Import''' rules, like the use of a single '''flag''' column, applies to '''only the current snapshot'''Therefore, changing the '''Conditional Import''' rules for a down timeline '''snapshot''' will '''NOT''' change the look for all previous snapshots unless further '''Conditional Import''' rules changes are specifically made for these '''snapshots''' via the '''REPLACE snapshot''' procedure.
+
3) '''Conditional Import Filters''' is a powerful new capability that allows you to better control the content of your project viewsRepeated use of '''Conditional Import Filters''' makes project view composition and editing more efficient when you are preparing schedule visualization for presentations/discussions.
  
3) '''Conditional Import''' is a powerful new capability that allows you to better control the content of your project views.  '''Conditional Import''' also makes project views more useful in '''project schedule analysis''' presentations/discussions.  As such, OnePager becomes not only a '''presentation''' tool but an addition to your suite of project schedule '''analysis''' tools.
+
===Using Text Fields with Conditional Import Filters===
  
===When Microsoft Project Source Plans are Read-Only===
+
4) Suppose you want to create a project view that only shows the tasks/milestones associated with a certain '''Phase''' of the project.  If the data are represented in the '''source plan''' as shown below in the '''Text30''' field, this is easily done.
  
4) Occasions may also arise where you are not able to modify a Microsoft Project source plan.  For instance, with a read-only file you might be unable to add the required '''import''' control '''flag''' columns or be unable to change them. You would have to first import all rows and manually edit out or hide the unwanted row tasks/milestones after the project view is created.  Again, version 6.0 allows you to specify '''import conditions''' that meet your needs, say, only the rows which correspond to a particular project '''Phase''' for which there are data already available in the plan’s source file.  The example below will illustrate this:
+
:a) Consider the Microsoft Project '''source plan''' just below where '''Text30''' field is displayed which corresponds to the user's '''Phase''' data field:
  
:a) Consider the Microsoft Project source plan just below which has no '''flag''' field columns defined and happens to be Read-only:
+
<center>[[File:P60-7_18_1-60-(7AA)-04252017.png]]</center>
 +
<!--<center>P60-7_18_1-60-(7AA)-04252017.png</center>-->
  
<center>[[File:P60-7_18_1-60-(7)-09242016.png]]</center>
 
<center>P60-7_18_1-60-(7)-09242016.png</center>
 
  
:b) For the sake of this example, we will assume that '''Flag1''' through '''Flag20''' are not defined and have no data in the rows even if these columns are hidden in Microsoft Project.  You need, again for illustration, something to control the '''import''' of rows.  We’ll use the '''Phase''' column from the source plan which happens to be the Microsoft Project '''Text30''' column.
+
:b) Your desire is to create a project view with tasks/milestones displayed from the '''Phase II''' portion of the project.  We’ll use the '''Text30''' field from the '''source plan'''.
  
 
:c) Following the same sequences as in the previous example, we’ll launch '''OPP''' from the Microsoft Project tool bar, select the '''NEW''' option from the '''OnePager Start''' form, and make project view name and snapshot date modifications to the '''OPC''' form as shown below:
 
:c) Following the same sequences as in the previous example, we’ll launch '''OPP''' from the Microsoft Project tool bar, select the '''NEW''' option from the '''OnePager Start''' form, and make project view name and snapshot date modifications to the '''OPC''' form as shown below:
  
 
<center>[[File:P60-7_18_1-60-(8A)-12272016.png]]</center>
 
<center>[[File:P60-7_18_1-60-(8A)-12272016.png]]</center>
<center>P60-7_18_1-60-(8A)-12272016.png</center>
+
<!--<center>P60-7_18_1-60-(8A)-12272016.png</center>-->
  
:d) In the Microsoft Project source plan there are a total of six (6) possible '''Phase''' names.  In this example, we’ll use '''Conditional Import''' to just build a project view showing '''Phase II''' task and milestones by creating a '''Conditional Import '''rule that looks like this:
+
:d) In the Microsoft Project '''source plan''' there are several possible '''Phase''' names.  In this example, we’ll use '''Conditional Import Filters''' to just build a project view showing '''Phase II''' task and milestones by creating a '''Conditional Import Filters''' rule that looks like this:
  
<center>[[File:P60-7_18_1-60-(9A)-12272016.png]]</center>
+
<center>[[File:P60-7_18_1-60-(9BB)-03022017.png]]</center>
<center>P60-7_18_1-60-(9A)-12272016.png</center>
+
<!--<center>P60-7_18_1-60-(9BB)-03022017.png</center>-->
  
:e) This simple '''Conditional Import''' rule gives you access to all the tasks associated with '''Phase II'''.  So, click the '''OK '''button on the above form and then click the '''Create project view''' button on the '''OPC''' form to create the project view as shown below:
+
:e) This simple '''Conditional Import Filters''' rule gives you access to all the tasks associated with '''Phase II'''.  So, click the '''OK''' button on the above form and then click the '''Create project view''' button on the '''OPC''' form to create the project view as shown below:
  
 
<center>[[File:P60-7_18_1-60-(10)-09242016.png]]</center>
 
<center>[[File:P60-7_18_1-60-(10)-09242016.png]]</center>
<center>P60-7_18_1-60-(10)-09242016.png</center>
+
<!--<center>P60-7_18_1-60-(10)-09242016.png</center>-->
  
5) Since '''OPP''' was told to generate the legend using the '''Resource Names''' column from the Microsoft Project source plan, you see that only one phase name is displayed. '''Team 2''' is shown in the legend as the only resource name participating in '''Phase II''' of the project. Using '''Conditional Import''' first overcomes any difficulty dealing with a Read-only file and, second, allows you to '''focus''' on the second phase of the project to see the details in the plan.  In this case, the resources assigned. Again, '''Conditional Import''' becomes an '''analysis''' aid as well as a '''presentation''' aid.
+
5)  Using '''Conditional Import Filters''' as shown above allows you to '''focus''' on the second phase of the project to see the details in the plan.  In this case, the resources assigned.
<!--
+
===Analysis Using an Existing Project View===
+
 
+
6) There are also occasions where you may want to go back '''AFTER''' a project view is created and '''update''' the project view to look at rows controlled by another '''flag''' column.  You may also want to build project views to do some '''analysis''' on the project schedule.  This is easily done '''AFTER''' the project view is created by looking at other logical relationships within the Microsoft Project source plan data. 
+
 
+
====Changing the Flag Field AFTER the Project View is Created====
+
 
+
7) Making changes to the '''flag''' field column after a project view is created is quite easy using the controls from the OnePager '''Project View Editor’s''' '''Data''' tab.
+
 
+
:a) First, launch Microsoft Project with the original source plan and click the '''OnePager''' button on the Microsoft Project tool bar.  Then, click the '''UPDATE''' button on the '''OnePager Start''' form. This will load the project view into the '''OPP’s''' '''Project View Editor''' ('''PVE''').
+
 
+
:b) With the '''PVE''' running, go to the '''Data tab''' and click the '''Custom Update''' button which brings up the '''OPC''' form shown in the illustration below. 
+
 
+
:c) In this form, make sure the '''Select tasks with ‘Yes’ in column''' button is on, click the dropdown menu, and select the alternate '''flag''' field column as shown below:
+
 
+
<center>[[File:P60-7_18_1-60-(11)-09242016.png]]</center>
+
<center>P60-7_18_1-60-(11)-09242016.png</center>
+
 
+
:d) In the above project view, which was created originally using '''Custom Import''' rules, you are changing the '''import''' control back to a defined '''flag '''column, specifically, '''Flag10'''.  When you do this and '''REPLACE''' the snapshot you get the following message from OnePager:
+
 
+
<center>[[File:P60-7_18_1-60-(12)-11282016.png]]</center>
+
<center>P60-7_18_1-60-(12)-1128016.png</center>
+
 
+
:e) This message is a reminder of what you are about to do to the snapshot you are about to '''replace'''.  To continue, click the '''Continue import''' button and OnePager will generate the updated project view as shown here
+
 
+
<center>[[File:P60-7_18_1-60-(12A)-11282016.png]]</center>
+
<center>P60-7_18_1-60-(12A)-11282016.png</center>
+
 
+
:f) The above '''replacement''' snapshot was built with the '''Flag10''' column controlling the '''re-import''' of Microsoft Project source plan file data.  The previous '''import''' rules are overridden and the snapshot is '''REPLACED''' in the project view.  This example illustrates how you can revert from using '''Conditional Import''' rules to the more conventional use of '''flag''' columns to control '''import'''.
+
 
+
====Changing Custom Import Rules AFTER the Project View is Created====
+
 
+
8) As was mentioned earlier, before version 6.0, handling '''import '''condition change situations meant totally starting over by going back to the '''OnePager Start''' form and selecting a different '''flag''' column.  Version 6.0 lets you change the '''import conditions''' from the '''PVE''' by using the '''Data tab’s Custom Update''' button to access your '''Conditional Import''' rules and edit them.  Here’s how changing '''Conditional Import''' rules can be done '''AFTER''' the project view is created:
+
 
+
:a) Consider the previous example where you wanted to create a project view consisting of tasks/milestones with '''Start''' dates later than 10/11/2015 and earlier than 12/31/2015.  Suppose you have that project view in the '''PVE''' and you want to '''import''' tasks/milestones for display that have '''Finish''' dates less than 11/30/2015. 
+
 
+
:b) You can do this by first bringing up the project view from Microsoft Project by launching OnePager and clicking the '''UPDATE''' button in the '''OnePager Start''' form.  This brings up the '''PVE''' displaying the project view with the two '''Start''' date '''Conditional Import Rules''' defined previously.
+
 
+
:c) Next, go to the '''Data tab''', click the '''Custom Update''' button bringing up the '''OPC''' form created in a previous example.
+
 
+
:d) Then, click the '''Edit Filters…''' button to bring up the '''Conditional Import Rules''' form which displays the two rules.  You can now modify the '''Conditional Import''' rules by '''Adding''' a new rule as shown below:
+
 
+
<center>[[File:P60-7_18_1-60-(13)-11282016.png]]</center>
+
<center>P60-7_18_1-60-(13)-11282016.png</center>
+
 
+
:e) Now, click '''OK''' on the '''Conditional Import Rules''' form to return to the '''OPC''' form where you should click the '''REPLACE existing snapshot at date''' button as shown below:
+
 
+
<center>[[File:P60-7_18_1-60-(14)-11282016.png]]</center>
+
<center>P60-7_18_1-60-(14)-11282016.png</center>
+
 
+
:f)  Then, click the '''Replace dates''' button on the '''OPC '''form and the following project view will appear:
+
 
+
<center>[[File:P60-7_18_1-60-(16)-11282016.png]]</center>
+
<center>P60-7_18_1-60-(16)-11282016.png</center>
+
 
+
:g) Looking at the project view above, we see that all the '''Conditional Import''' rules specified are met.
+
 
+
9)  As a summary, with OnePager version 6.0 and its '''Conditional Import''' feature you are now able to have more flexibility importing source plan file data when the project view is originally created, revert back to using '''Flag''' fields '''AFTER''' the project view is created, and, again, use '''Conditional Import''' rules, to '''replace or add''' snapshots '''AFTER''' the project view is created.
+
 
+
10) For more detailed instructions regarding using '''Conditional Import''' please go to the following (Portal) link:  [[Conditional Import for Version 6.0 (Portal) | Conditional Import (Portal)]] 7.18.1-60.
+
-->
+
  
 
==Related Links:==
 
==Related Links:==
Line 140: Line 78:
 
[[Basic Workflows for Version 6.0 (Portal) | Basic Workflows (Portal)]]
 
[[Basic Workflows for Version 6.0 (Portal) | Basic Workflows (Portal)]]
  
[[Conditional Formatting for Version 5.3 (Portal) | Conditional Formatting (Portal)]]   Point to Version 6.0 Later
+
[[Conditional Formatting for Version 6.0 (Portal) | Conditional Formatting (Portal)]] <!--11.0.1-60-->
  
[[Using the OnePager "Data" Tab's "Selected file(s)" Button for Version 6.0 | Using the OnePager "Data" Tab's "Selected file(s)" Button]]
+
[[Using the OnePager "Data" Tab's "Selected file(s)" Button for Version 6.0 | Using the OnePager "Data" Tab's "Selected file(s)" Button]] <!--7.17.1-60-->
  
[[OnePager Express Import of Data from Microsoft Excel]]
+
[[OnePager Express Import of Data from Microsoft Excel for Version 6.0 | OnePager Express Import of Data from Microsoft Excel]] <!--4.4-60-->
  
 
[[Message to Assist with Setting Import Flags When No Data Are Imported]]
 
[[Message to Assist with Setting Import Flags When No Data Are Imported]]
  
[[Understanding Project Views and Snapshots for OnePager Pro]]
+
[[Understanding Project Views and Snapshots for OnePager Pro for Version 6.0 | Understanding Project Views and Snapshots for OnePager Pro]] <!--4.1-60-->
  
[[Understanding Project Views and Snapshots for OnePager Express]]
+
[[Understanding Project Views and Snapshots for OnePager Express for Version 6.0 | Understanding Project Views and Snapshots for OnePager Express]] <!--4.2-60-->
  
 
(0.4.1.1-60)
 
(0.4.1.1-60)
Line 157: Line 95:
 
[[Category:Add-in]]
 
[[Category:Add-in]]
 
[[Category:Basic Workflows]]
 
[[Category:Basic Workflows]]
[[Category:Conditional Import]]
+
[[Category:Conditional Import Filters]]
 
[[Category:Importing]]
 
[[Category:Importing]]
 
[[Category:Project Views]]
 
[[Category:Project Views]]

Latest revision as of 14:39, 19 May 2017

About Conditional Import Filters for OnePager

In OPP and OPX version 6.0, the capability for you to control the import of rows from your source plan is made even more flexible with the new Conditional Import Filters capabilities. Here we overview some situations you may have encountered in the past with OnePager that can be facilitated better with Conditional Import Filters.

When a Flag Field Isn’t Sufficient

1) There are occasions where you would like to import a source plan row but only when the contents of a specified field holds a desired value or range of values. In this case, using a flag field may not be flexible enough or may be too time consuming.

2) Suppose you want to include source plan rows where task/milestone Start dates are greater than a specified date. With version 6.0 you can specify, in a Conditional Import Filters rule, the conditions that meet any logical combination of criteria. Here’s how it works:

a) We’ll use the BlueGrass Project 2J-303 Microsoft Project source plan as an example. Recall that the field headers look something like this:
P60-7 18 1-60-(1)-09242016.png
c) The OnePager choices (OPC) form below has an additional radio button in the Task Selection group, Select tasks by custom filter, and a new button called Edit filter…. Before clicking the Select tasks by customer filter button, the OPC form looks like this:
P60-7 18 1-60-(3A)-12272016.png
d) Now, click the Select tasks by custom filter button. When you do, a blank Custom Import Rules form will appear as show below:
P60-7 18 1-60-(4BB)-03022017.png
e) You can now compose the two rules needed to import rows that have Start dates greater than 10/11/2015 but less than 12/31/2015. When you do this, the Conditional Import Rules form will look like this:
P60-7 18 1-60-(5BB)-03022017.png
f) Note that the All of the following rules are true radio button is selected so that the two rules are essentially an AND operation. When you click OK on the form, this form will disappear and you will be back at the OPC form once more. Now, click the Create new project view button and OPP will create the project view that looks like this:
P60-7 18 1-60-(6)-09242016.png
g) In the project view above, there are tasks that extend beyond 12/31/2015 but there are no tasks that Start on or after 12/31/2015. Similarly, there are no tasks that Start before 10/11/2015.
h) When the project view is saved, the Conditional Import Filters rules are saved as well and will be used to control the import for subsequent snapshots. Further, the Conditional Import Filters rules can be edited (i.e., changed, added, or deleted). When such changes are made to the Conditional Import Filters rules, any new snapshot or snapshot being replaced will be configured by the active set of Conditional Import Filters rules. Finally, you can always revert to using flag fields or select All tasks for import.

3) Conditional Import Filters is a powerful new capability that allows you to better control the content of your project views. Repeated use of Conditional Import Filters makes project view composition and editing more efficient when you are preparing schedule visualization for presentations/discussions.

Using Text Fields with Conditional Import Filters

4) Suppose you want to create a project view that only shows the tasks/milestones associated with a certain Phase of the project. If the data are represented in the source plan as shown below in the Text30 field, this is easily done.

a) Consider the Microsoft Project source plan just below where Text30 field is displayed which corresponds to the user's Phase data field:
P60-7 18 1-60-(7AA)-04252017.png


b) Your desire is to create a project view with tasks/milestones displayed from the Phase II portion of the project. We’ll use the Text30 field from the source plan.
c) Following the same sequences as in the previous example, we’ll launch OPP from the Microsoft Project tool bar, select the NEW option from the OnePager Start form, and make project view name and snapshot date modifications to the OPC form as shown below:
P60-7 18 1-60-(8A)-12272016.png
d) In the Microsoft Project source plan there are several possible Phase names. In this example, we’ll use Conditional Import Filters to just build a project view showing Phase II task and milestones by creating a Conditional Import Filters rule that looks like this:
P60-7 18 1-60-(9BB)-03022017.png
e) This simple Conditional Import Filters rule gives you access to all the tasks associated with Phase II. So, click the OK button on the above form and then click the Create project view button on the OPC form to create the project view as shown below:
P60-7 18 1-60-(10)-09242016.png

5) Using Conditional Import Filters as shown above allows you to focus on the second phase of the project to see the details in the plan. In this case, the resources assigned.

Related Links:

Basic Workflows (Portal)

Conditional Formatting (Portal)

Using the OnePager "Data" Tab's "Selected file(s)" Button

OnePager Express Import of Data from Microsoft Excel

Message to Assist with Setting Import Flags When No Data Are Imported

Understanding Project Views and Snapshots for OnePager Pro

Understanding Project Views and Snapshots for OnePager Express

(0.4.1.1-60)‏‎