Conditional Import for OnePager Pro Desktop for Version 6.0

Overview

An overview article with examples is available at Conditional Import Filters for OnePager . That article is recommended reading before you advance to this article or any other of the product specific articles in this series.

This article provides information details on the use of the Conditional Import Filters feature for OnePager Pro (OPP) Desktop edition.

(1) First, we’ll provide information on how to create Conditional Import Filters rules using the Conditional Import Rules form.

(2) Then, we’ll cover how to create a NEW project view from the OnePager Pro’s (OPP) Desktop OnePager Start form. Further on, we’ll cover how to use Conditional Import Filters with the OnePager Start form’s UPDATE and OPEN modes.

(3) Finally, we’ll provide details on how Conditional Import Filters works with (a) Microsoft Project Integrated Master Schedules (IMS), (b) with Microsoft Project source plan consisting of a package of separate files, and (c) with server resident Microsoft Project source plan.

Adding a Filter Rule to the Conditional Import Rules Form

1) The Conditional Import Rules form resembles to the OPP Conditional Formatting form in look and function. It is with this form that you can specify, add, copy, change, and delete Conditional Import Filters rules. The form is accessed from the OnePager choices (OPC) form as shown below:

a) The Conditional Import Rules form is shown in its initial blank state above. The rules entered into the Conditional Import Rules form becomes part of any project view subsequently created or updated and are saved with the project view. . If you later on, create or update a snapshot using a flag field, OPP will save the flag field and clear the Conditional Import Filters rules.

b) Conditional Import Filters rules are typically entered when a project view is first created through the NEW workflow mode.

c) After a project view is created, without Conditional Import Filters rules previously defined, rules may be added later through the UPDATE process invoked either from the OnePager Start form or from the Project View Editor (PVE) Data tab’s Custom Update button. These processes are described later in this article.

2) With the Custom Import Rules form visible and blank, click the Add Rule button which will create a new row in the Custom Import Rules form as shown below:

a) There are five cells shown for the new rule row above. The first two cells are used as follows:

i) The first two cells are used as selection cells.

ii) The first left-most cell, when clicked, allows you to use the Copy Rule(s) or the Delete Rule(s) buttons.

iii) The second cell from the left is a checkbox used to allow you to activate (checkbox checked) or deactivate (checkbox unchecked) the rule. If the checkbox is unchecked, OPP will not apply the rule when performing the import function.

b) The Field cell of a row (third from the left) has a dropdown menu that allows you to select a Microsoft Project source plan field to use in creating the new logical relationship. When the dropdown menu is selected, the Field cell will look something like this:

c) When a Microsoft Project source plan field is selected, the name will be displayed in the Field cell of the new Custom Import rule row.

d) The look of the rest of the new Conditional Import rule row depends on the type of the Microsoft Project source plan field selected. These types are discussed next.

3) Date and Numeric Fields – When Microsoft Project date or numeric types are entered in the Field cell of the Conditional Import Filters rule row, the Operator field dropdown will provide the options shown below:

a) These are the conventional six (6) logical operators used consistently in OPP for date and numeric types. They are the same Operators used in OPP for Conditional Formatting. See the article at Conditional Formatting Overview for OnePager Pro for complimentary details on the use of these logical operators.

b) For the logical statement to be TRUE, hence cause OPP to import the corresponding Microsoft Project source plan row, the contents of the Value field in the Conditional Import Filters rule row must match the type and value in the Microsoft Project source plan’s. Additionally, the logical relationship must be TRUE for OPP to act on the condition.

4) Text Fields – When Microsoft Project text types are entered in the Field cell of the Conditional Import Filters rule row, the Operator field dropdown will provide the options shown below:

a) These are the conventional four (4) logical operators used consistently in OPP for the text type. They are the same Operators used in OPP for Conditional Formatting. See the article at Conditional Formatting Overview for OnePager Pro for complimentary details on the use of these logical operators.

b) For the logical statement to be TRUE, causing OPP to import the corresponding Microsoft Project source plan row, the contents of the Value cell in the Conditional Import Filters rule row must match the type and value in the Microsoft Project source plan’s. Additionally, the logical relationship must be TRUE to make OPP act on the condition.

5) Boolean Fields – When Microsoft Project Boolean types are entered in the Field cell of the Conditional Import Filters rule row, the Operator field dropdown will provide the options shown below:

a) These are the two (2) conventional Boolean logical operators used consistently in OPP for the Boolean type. They are the same Operators used in OPP for Conditional Formatting. See the article at Conditional Formatting with Boolean Fields for OnePager Pro for complimentary details on the use of these logical operators.

b) Boolean types are a special case as the operator and the value in OPP are combined into one cell of the Conditional Import rule row - the Operator cell.

c) For the logical statement to be TRUE, hence cause OPP to import the corresponding Microsoft Project source plan row, the contents of the Operator cell in the Conditional Import Filters rule row must match the type and value in the Microsoft Project source plan’s. Additionally, the logical relationship must be TRUE to make OPP act on the condition.

6) Flag1 Through Flag20 Fields – OPP recognizes Microsoft Project Boolean Flag1 through Flag20 as Boolean types as well. When these Microsoft Project types are entered in the Field cell of the Conditional Import Filters rule row, the Operator cell dropdown will provide the options shown below:

a) As mentioned above, these are the two (2) conventional Boolean logical operators used consistently in OPP for the Boolean type. They are the same Operators used in OPP for Conditional Formatting. See the article at Conditional Formatting with Boolean Fields for OnePager Pro for complimentary details on the use of these logical operators.

b) We mention Flag1 through Flag20 specifically here because you will see that these Microsoft Project Boolean fields can be used in conjunction with other Microsoft Project Fields to construct more complex sets of Conditional Import Filters rules. Recall that the OPC form has a specific button for using Flag1 through Flag20 or Numeric type fields containing only zero (0) or one (1) values called Select task with ‘Yes’ in field: for use specifically when you want to use flag fields to control import ONLY.

c) We want to emphasize the flexibility that Conditional Import Filters has added to the way you can import rows from your Microsoft Project source plan. You can, therefore, formulate sets of Conditional Import Filters rules to controls imports using all available types of Microsoft Project fields.

d) As before, for the logical statement to be TRUE, causing OPP to import the corresponding Microsoft Project source plan row, the contents of the Operator cell in the Conditional Import Filters rule row must match the type and value in the Microsoft Project source plan’s. Additionally, the logical relationship must be TRUE to make OPP act on the condition.

Editing an Existing Filter Rule in the Conditional Import Rules Form

7) Suppose you’ve composed several Conditional Import Filters rules in an open Conditional Import Rules form as shown below:

a) Now further suppose, after reviewing these two rules, that you realize that you may not be able to capture any tasks/milestones that happen to Start on 12/31/2015 because the current rule is based on the less than logical Operator.

b) To make the change in the Operator cell, click on the cell’s contents which will highlight the cell in blue and reveals the dropdown menu button which you should click. When you do the Conditional Import Rules form should look like this:

c) To change the rule, click the desired Operator in the dropdown menu, in this case the less than or equal Operator, and it will be displayed in the Operator cell of the second rule as shown here:

d) Any Field, Operator, or Value cell may be edited in this way. Additionally, the On cell may be toggled to control the Conditional Import Filters rule rows participation in the import process. Finally, you may switch between the two radio buttons at the top of the form in order to change the relationship between the rules from OR to AND or vice versa.

e) The edits described above may be made to the Conditional Import Rules form regardless of the OPC mode in which you are working (i.e., NEW, UPDATE, OPEN). Also, you may bring up the Conditional Import Rules form from the OPC form as many times as needed to accomplish your presentation goal. OPP save the content of the last edit you make to the Conditional Import Rules form.

f) When satisfied with the structure of your import rules, click the OK button at the bottom of the form to return to the OPC form. Now you are ready to create a new project view.

Copying an Existing Filter Rule in the Conditional Import Rules Form

8) The Copy Rule(s) button is provided in the Conditional Import Rules form to facilitate the creation of additional rules.

a) To copy a rule to create a new rule, first select the rule row from which you wish to copy as shown below:

b) Once the desired row is selected, clicking the Copy Rule(s) button will copy the contents of the rule selected as indicated by the highlighted left-most cell in the desired rule as shown below:

c) At this point you may edit the new (copied row) in the manner described in the previous sub-section. When you are finished, the new set of three rule rows may look like this:

d) When satisfied with the structure of your import rules, click the OK button at the bottom of the form to return to the OPC form. Now you are ready to create a new project view.

Deleting an Existing Filter Rule in the Conditional Import Rules Form

9) There are times when a particular Conditional Import Filters rule will no longer serve its purpose. You can select the rule row to be deleted and click the Delete Rule(s) button.

a) The process for deleting a rule parallels the process for copying a rule row in that the you must select the desired row to delete by clicking the left-most cell in that rule’s row.

b) Once the selection is made, click the Delete Rule(s) button and OPP will first put up a warning message asking if you really want to delete the rule row as shown below:

c) If you select the No option, OPP will abandon the rule row deletion operation and the warning message will disappear leaving the selected rule row still selected.

d) If you select the Yes option, OPP will remove the warning message, delete the selected rule row, and leave the Conditional Import Rules form showing the remaining rule rows, if any. At this point, you may, Add Rules, Copy Rules, Delete Rules, or Edit Rules as you wish.

e) When satisfied with the structure of your import rules, click the OK button at the bottom of the form to return to the OPC form.

Using Conditional Import Filters Rules When Creating NEW Project Views

1) Using Conditional Import Filters rules in the process of creating a NEW project view was partially covered in the first section above ( Overview). In this section we’ll add a bit more detail.

Using Conditional Import Filters Rules from the OnePager Start Form’s NEW Mode

2) When creating a NEW project view, follow the workflow process provided in this article: Creating a NEW Project View - OnePager Pro Desktop .

a) First, launch the OnePager Pro Desktop application which brings up the OPP Desktop application as shown below:

File:P60-7 18 1 2-60-(12AA)-12292016.png

b) Then, click the NEW button on the OnePager Start form shown below:

Switching from Flag Fields to New Conditional Import Filters Rules

c) When you click the NEW button, the OPC form will appear as shown below. The process for building a new project view with Conditional Import Filters is the same with the exception that instead of using flag field from your Microsoft Project source plan you will, instead, invoke the Conditional Import Rules form from the OPC form as shown below:

d) In the illustration above, in the Task Selection section of the form, the Select task by custom filter radio button is clicked. This action brings up the Conditional Import Rules form also shown above.

e) At this point you may Add Rules to the form, Copy Rules, or Delete Rules or edit existing rules.

Switching from Conditional Import Filters Rules to Flag Fields or Selecting all Tasks

3) If you subsequently decide after composing one or more Conditional Import Filters rules and clicking OK on the Conditional Import Rules form that you want to use flag fields instead, you may revert back to either of the two other Task Selection options provided in the OPC form shown above.

a) To do this, click either of the other two radio buttons to Select all tasks, or Select task with ‘Yes’ in field:

b) When you click the Select all tasks button there is no further action you need to take on the OPC form save entering the project view name and selecting a Snapshot Date as required. Creating the project view is a matter of clicking the Create new project view button at the bottom of the OPC form.

c) However, if you click the Select tasks with ‘Yes’ in field: you will be asked to select a field from your Microsoft Project source plan as shown below:

d) When you have selected the desired flag, updated the project view name, and/or updated the snapshot date, you are ready to create the project view.

e) In these circumstances where you’ve switched from using Conditional Import Filters rules to either selecting all tasks, or selecting tasks using a flag field, OPP will discard any Conditional Import Filters rules associated with the project view.

Adding, Editing, Copying, and Deleting Conditional Import Filters Rules

4) Managing Conditional Import Filters rules was discussed in previous sub-sections of this article. Please follow the reference links provided below for details on adding, editing, copying, and deleting of Conditional Import Filters rules:

a) Adding a new rule: Adding a Filter Rule to the Conditional Import Rules Form.

b) Editing an existing rule: Editing an Existing Filter Rule in the Conditional Import Rules Form.

c) Copying a rule: Copying an Existing Filter Rule in the Conditional Import Rules Form.

d) Deleting a rule: Deleting an Existing Filter Rule in the Conditional Import Rules Form.

Using Conditional Import Filters Rules When UPDATING a Project Views

Conditional Import Filters can also be done in the OPP UPDATE mode regardless of whether the original project view was itself created with Conditional Import Filters rules.

(1) Normally, when UPDATING a project view with Conditional Import Filters rules, this will be done when the OPC form is invoked from the OnePager Start form when the UPDATE button is clicked.

(2) However, it is also possible to update a project view from the Project View Editor (PVE) as we will also explain in this sub-section.

Using Conditional Import Filters Rules from the OnePager Start Form’s UPDATE Mode

1) After a project view is created either with or without Conditional Import Filters rules, it is still possible to update the next and following snapshots in a project view with Conditional Import Filters rules.

a) Suppose we have a project view that was created and used previously and originally built using Microsoft Project flag fields to control the import of tasks and milestones to the project view. By making a change to the OPC form when the update process is started, you can change the new snapshot in the project view to show different tasks by using Conditional Import Filters rules to replace the previously used Microsoft Project flag fields. This update can be applied either to create a NEW snapshot or REPLACE an existing snapshot.

b) First, launch OnePager Pro Desktop application. This brings up the OnePager Start form where you should click the UPDATE button and select the project view from either the RECENT or the BROWSE FILES… option as shown below:

File:P60-7 18 1 1-60-(14)-09272016.png

c) The project view selected was originally created using a Microsoft Project flag field as shown in the OPC form which appeared after the above UPDATE button is clicked and the project view selected from the RECENT list show above. The OPC form is shown below:

File:P60-7 18 1 1-60-(15)-09272016.png

d) Make sure that you have selected either the NEW or REPLACE mode in the Snapshot Date section of the OPC form and set the appropriate snapshot date.

e) Then, to begin that portion of the process to use Conditional Import Filters rules, click the Select tasks by custom filter radio button which immediately brings up the Custom Import Rules form which is blank as shown below:

f) You are now ready to create your Conditional Import Filters rules.

2) Please refer to the following sub-section of this article for guidance on adding, editing, copying, and deleting Conditional Import rules: Adding, Editing, Copying, and Deleting Conditional Import Filters Rules.

3) Clicking the New button in the OPC form above will create a new snapshot with the appropriate snapshot date using the Conditional Import Filters rules you’ve specified.

a) Only this new snapshot will have a look corresponding to the Microsoft Project source plan rows imported under the control of the Conditional Import Rules form.

b) Warning: Since OPP only maintains one source plan row selection mechanism, previous snapshots may take on a different set of tasks/milestones, swimlanes, and row text columns. Accordingly, great care should be taken when adopting this process.

c) As long as new subsequent snapshots are created with the current set of Conditional Import Filters rules, these snapshots will have the same Microsoft Project source plan rows imported.

4) Snapshots that are REPLACED will take on the look of snapshots controlled by the current set of Conditional Import Filters rules.

5) Later on, perhaps after the project view was updated several times in later Microsoft Project source plan update cycles, you may want to go back to using Microsoft Project flag fields.

a) If this is require, simply repeat the front end of the UPDATE process and when the OPC form appears click the Select all tasks radio button.

b) You can also choose to click the Select tasks with ‘Yes’ in field: radio button and select the appropriate flag field from the dropdown menu which is available.

c) In either of the above two cases, OPP will clear all the Conditional Import Filters rules that were in the Conditional Import Rules form so that they will not be available later.

6) The UPDATE process allows you to create a NEW snapshot at date… as well as REPLACE existing snapshots at date….

a) If Conditional Import rules are being used (active) at the time the current snapshot is being readied for processing in the PVE and after the New or Replace… button is clicked at the bottom of the OPC form, the Conditional Import Filters rules will be applied regardless of whether the New or Replace… option is selected.

b) Warning: Since OPP only maintains one source plan row selection mechanism, previous snapshots may take on a different set of tasks/milestones, swimlanes, and row text columns. Accordingly, great care should be taken when adopting this process.

c) Furthermore, since Conditional Import Filters is snapshot dependent, and as mentioned earlier, only the snapshot in the PVE will be impacted.

Using Conditional Import Filters Rules with the Custom Update… Button on the Data Tab in UPDATE Mode

7) In the previous sub-section, setting up to do a Conditional Import Filters of an existing project view was done from the OPC form which allows you to do the import before the project view is turned over to the PVE for display and editing. OPP also supports setting up and performing Conditional Imports Filters after the project view under UPDATE is already displayed in the PVE.

a) Suppose, we have a project view that we want to update that was previously built using a Microsoft Project flag field to control the import. Further, suppose, that this project view was previously updated through several cycles such that it now contains several snapshots all produced with the same Microsoft Project flag field controlling the import.

b) Finally, suppose that you want to produce another snapshot again using the same flag field to initially control the import, but after the project view reaches the PVE you would like to “experiment” with the graph by importing other rows from the Microsoft Project source plan.

c) Now with this scenario in mind, we can use the ADD a Snapshot workflow (See the article at: ADDING a Snapshot via Pull Operation - OnePager Pro ) to get the project view into the PVE under control of the existing flag field. Once the project view is in the PVE we can then perform an update to bring additional rows from the Microsoft Project source plan to “experiment” with the project view.

8) First, launch OnePager Pro Desktop. This brings up the OnePager Start form where you should click the UPDATE button and select the project view from either the RECENT or the BROWSE FILES… option as shown below:

File:P60-7 18 1 1-60-(19)-10032016.png

a) Selecting this project view for update with the UPDATE button shown above will bring up the OPC form shown below:

File:P60-7 18 1 1-60-(20)-10032016.png

b) At this point you want to create a new snapshot using Conditional Import Filters rules. To do this, first make sure that the NEW snapshot at date radio button is selected in the Snapshot Date section of the above for and set the snapshot date to a new date as shown below:

File:P60-7 18 1 1-60-(21)-10032016.png

c) Now, click the New button at the bottom of the OPC form. This action will create a new snapshot with the new snapshot date shown above. This new snapshot is shown below:

File:P60-7 18 1 1-60-(22A)-12282016.png

d) Now with the new snapshot showing in the PVE, go to the Data tab and click the Custom Update button as shown here:

File:P60-7 18 1 1-60-(23A)-12282016.png

e) Next, click the Select task by custom filter button in the Task Selection section of the OPC form. This action will bring up an empty Custom Import Rules form as shown here:

File:P60-7 18 1 1-60-(24BB)-03032017.png

f) In the Conditional Import Rules form add the rules you require to make the new snapshot display the rows you need the Microsoft Project source plan as we’ve done below:

File:P60-7 18 1 1-60-(25A)-12282016.png

g) When the Conditional Import Filters rules are satisfactory, click the OK button at the bottom of the form which will collapse the Conditional Import Rules form into the OPC form. Now, click the Replaced button on the OPC form to create the revised snapshot as shown below:

File:P60-7 18 1 1-60-(26A)-12282016.png

h) The updated project view above is a snapshot created from the open Microsoft Project source plan using the import controls you specified in the Conditional Import Rules form you accessed. The process works similarly for Replacing an existing snapshot.

9) Care must be taken when REPLACING a snapshot to assure that OPP will have access to the correct Microsoft Project source plan corresponding to the snapshot date you wish to replace.

a) Warning: Since OPP only maintains one source plan row selection mechanism, previous snapshots may take on a different set of tasks/milestones, swimlanes, and row text columns'. Accordingly, great care should be taken when adopting this process.

b) Using Conditional Import Filters rules can, therefore, be considered the same as using flag fields with it comes to creating/replacing snapshots.

Using Conditional Import Filters Rules When OPENING a Project Views

Conditional Import Filters can also be done in the OPP OPEN mode regardless of whether the original project view was itself created with Conditional Import Filters rules.

(1) Normally, when OPENING a project view with Conditional Import Filters rules, this will be done when the OPC form is invoked from the OnePager Start form when the OPEN button is clicked.

(2) As seen from the discussion in the previous section Using Conditional Import Filters Rules with the Custom Update… Button on the Data Tab in UPDATE Mode, it is also possible to update a project view from the Project View Editor (PVE).

Using Conditional Import Filters Rules from The OnePager Start Form’s OPEN Mode

1) After a project view is created either with or without Conditional Import Filters rules, it is still possible to update the next and following snapshots in a project view when Opening the project view.

a) Suppose we have a project view that was created, used previously, and originally built using Microsoft Project flag fields to control the import of tasks and milestones. By making a change to the OPC form after the project view is opened, it is possible to change the new snapshot in the project view to show different tasks by using Conditional Import Filters rules to replace the previously used Microsoft Project flag fields. This update can be applied either to create a NEW snapshot or REPLACE an existing snapshot.

b) First, launch OnePager Pro Desktop. This brings up the OnePager Start form where you should click the UPDATE button and select the project view from either the RECENT or the BROWSE FILES… option as shown below:

File:P60-7 18 1 2-60-(27)-10052016.png

c) The project view selected was originally created using a Microsoft Project flag field. The project view is shown below:

File:P60-7 18 1 1-60-(28)-10032016.png

d) To satisfy your need to create a new snapshot controlled by some more complex import rules, you will need to click the Custom Update… button shown in the red box in the illustration above. When you do this the OPC form will appear as shown here:

File:P60-7 18 1 1-60-(29)-02032017.png

e) Make sure that you have selected either the NEW or REPLACE mode in the Snapshot Date section of the OPC form and set the appropriate snapshot date.

f) Then, to begin that portion of the process to use Conditional Import Filters rules, click the Select tasks by custom filter radio button which immediately brings up the Custom Import Rules form which is blank as shown below:

File:P60-7 18 1 1-60-(30CC)-03072017.png

g) You are now ready to create your Conditional Import Filters rules.

2) Please refer to the following sub-section of this article for guidance on adding, editing, copying, and deleting Conditional Import rules: Adding, Editing, Copying, and Deleting Conditional Import Filters Rules.

3) We’ve gone ahead and added two Conditional Import Filters rules to the Conditional Import Rules form as shown below:

File:P60-7 18 1 1-60-(31BB)-03072017.png

4) Clicking the New button in the OPC form above will create a new snapshot with the appropriate snapshot date using the Conditional Import Filters rules you’ve specified.

a) Only this new snapshot will have a look corresponding to the Microsoft Project source plan rows imported under the control of the Conditional Import Rules form.

b) Warning: Since OPP only maintains one source plan row selection mechanism, previous snapshots may take on a different set of tasks/milestones, swimlanes, and row text columns. Accordingly, great care should be taken when adopting this process.

c) As long as new subsequent snapshots are created with the new set of Conditional Import Filters rules, these snapshots will have the same Microsoft Project source plan rows imported.

d) The new snapshot under the control of the Conditional Import rules now looks like this:

File:P60-7 18 1 1-60-(26B)-12282016.png

5) Snapshots that are REPLACED will take on the look of snapshots controlled by the current set of Conditional Import Filters rules.

6) Later on, perhaps after the new project view was updated several times in later Microsoft Project source plan update cycles, you may want to go back to using Microsoft Project flag fields.

a) If this is require, simply repeat the front end of the UPDATE process and when the OPC form appears click the Select all tasks radio button.

b) You can also choose to click the Select tasks with ‘Yes’ in field: radio button and select the appropriate flag field from the dropdown menu which is available.

c) In either of the above two cases, OPP will clear all the Conditional Import Filters rules that were in the Conditional Import Rules form so that they will not be available later.

7) The UPDATE process allows you to create a NEW snapshot at date… as well as REPLACE existing snapshots at date….

a) If Conditional Import Filters rules are being used (active) at the time the current snapshot is being readied for processing in the PVE and after the New or Replace… button is clicked at the bottom of the OPC form, the Conditional Import Filters rules will be applied regardless of whether the New or Replace… option is selected.

b) Warning: Since OPP only maintains one source plan row selection mechanism, previous snapshots may take on a different set of tasks/milestones, swimlanes, and row text columns. Accordingly, great care should be taken when adopting this process.

Using Conditional Import Filters Rules with the Custom Update Button on the Data Tab in the OPEN Mode

8) In the previous sub-section, setting up to do a Conditional Import Filters of an existing project view was done from the OPC form which allows you to do the import before the project view is turned over to the PVE for display and editing. OPP also supports setting up and performing Conditional Imports after the project view is already OPENED and displayed in the PVE.

a) Suppose, we have a project view that we want to update that was previously built using a Microsoft Project flag field to control the import. Further, suppose, that this project view was previously updated through several cycles such that it now contains several snapshots all produced with the same Microsoft Project flag field controlling the import.

b) Finally, suppose that you want to produce another snapshot again using the same flag field to initially control the import, but after the project view reaches the PVE you would like to “experiment” with the graph by importing other rows from the Microsoft Project source plan.

c) Now with this scenario in mind, we can use the ADD a Snapshot workflow (See the article at: ADDING a Snapshot via Pull Operation - OnePager Pro ) to get the project view into the PVE under control of the existing flag field. Once the project view is in the PVE we can then perform an update to bring additional rows from the Microsoft Project source plan to “experiment” with the project view.

9) First, launch OnePager Pro Desktop. This brings up the OnePager Start form where you should click the OPEN button and select the project view from either the RECENT or the BROWSE FILES… option as shown below:

File:P60-7 18 1 2-60-(27)-10052016.png

a) When the project view is opened, it will look like this:

File:P60-7 18 1 1-60-(28)-10032016.png

b) To satisfy your need to create a new snapshot controlled by some more complex import filter rules, you will need to click the Custom Update… button shown in the red circle in the illustration above. When you do this the OPC form will appear as shown here:

File:P60-7 18 1 1-60-(29)-02032017.png

e) You are now ready to create your Conditional Import Filters rules.

10) Please refer to the following sub-section of this article for guidance on adding, editing, copying, and deleting Conditional Import rules: Adding, Editing, Copying, and Deleting Conditional Import Filters Rules.

11) We’ve gone ahead and added two Conditional Import rules to the Conditional Import Rules form as shown below:

File:P60-7 18 1 1-60-(31BB)-03072017.png

12) Clicking the New button at the bottom of the OPC form above will create a new snapshot with the appropriate snapshot date using the Conditional Import Filters rules you’ve specified.

a) Only this new snapshot will have a look corresponding to the Microsoft Project source plan rows imported under the control of the Conditional Import Rules form.

b) Warning: Since OPP only maintains one source plan row selection mechanism, previous snapshots may take on a different set of tasks/milestones, swimlanes, and row text columns. Accordingly, great care should be taken when adopting this process.

c) As long as new subsequent snapshots are created with the new set of Conditional Import Filters rules, these snapshots will have the same Microsoft Project source plan rows imported.

d) The new snapshot under the control of the Conditional Import Filters rules now looks like this:

File:P60-7 18 1 1-60-(26A)-12282016.png

13) Snapshots that are REPLACED will take on the look of snapshots controlled by the current set of Conditional Import Filters rules.

14) Later on, perhaps after the new project view was updated several times in later Microsoft Project source plan update cycles, you may want to go back to using Microsoft Project flag fields.

a) If this is require, simply repeat the front end of the UPDATE process and when the OPC form appears click the Select all tasks radio button.

b) You can also choose to click the Select tasks with ‘Yes’ in field: radio button and select the appropriate flag field from the dropdown menu which is available.

c) In either of the above two cases, OPP will clear all the Conditional Import Filters rules that were in the Conditional Import Rules form so that they will not be available later.

15) The UPDATE process allows you to create a NEW snapshot at date… as well as REPLACE existing snapshots at date….

a) If Conditional Import Filters rules are being used (active) at the time the current snapshot is being readied for processing in the PVE and after the New or Replace… button is clicked at the bottom of the OPC form, the Conditional Import Filters rules will be applied regardless of whether the New or Replace… option is selected.

b) Warning: Since OPP only maintains one source plan row selection mechanism, previous snapshots may take on a different set of tasks/milestones, swimlanes, and row text columns. Accordingly, great care should be taken when adopting this process.

Using Conditional Import Filters with Microsoft Project Integrated Master Schedules (IMS)

1) Integrated Master Schedules (IMS) in Microsoft Project are a common occurrence and OPP handles these quite effectively.

2) As a refresher please consult this article for information on how OPP builds graphs from Microsoft Project IMS source plans at: Making Multi-Project Graphs from MS Project Integrated Master Schedules .

3) Once a Microsoft Project IMS source plan is created, the selection of source plan rows for import to OPP is essentially the same as for single project Microsoft Project source plans. Using either flag fields or Conditional Import rules are applied to the entire source plan and OPP will create a graph according to the current Template once the source plan rows are imported.

4) Accordingly, the instructions provided in this article for single Microsoft Project source plans with respect to the OPP modes of NEW, UPDATE, and OPEN apply to Microsoft Project IMS source plans.

Using Conditional Import Filters with Multiple Separate Microsoft Project Source Plan Packages

1) Microsoft Project source plans that are grouped into packages for processing by OPP are treated as a single source plan entity from the perspective of import to OPP.

a) When a flag field is used to control the import of rows from multiple, separate Microsoft Project source plans grouped by OPP into a package, that flag field is applied to every single multiple Microsoft Project source plan uniformly in the package.

b) When Conditional Import Filters rules are being used to control the import of separate Microsoft Project source plans grouped by OPP into a package, the defined Conditional Import Rules form controls the import of rows from each of the separate Microsoft Project source plans in turn.

2) As a refresher please consult this article for information on how OPP builds graphs from multiple separate Microsoft Project source plans at: Making Multi-Project Graphs from Separate Microsoft Project Plans .

3) As with Microsoft Project IMS source plans, the instructions provided in this article for single Microsoft Project source plans with respect to the OPP modes of NEW, UPDATE, and OPEN apply to import from separate multiple Microsoft Project source plans.

Using Conditional Import Filters with Server Resident Microsoft Project Source Plan

1) When Microsoft Project source plans are accessed from servers in the “cloud” the source plans required are first down loaded into OPP before any defined flag field or Conditional Import Filters rules are applied. Therefore, import processing for server resident Microsoft Project source plans differs only from desktop computer resident source plan only in their location.

2) Please consult this article for information on how OPP accesses server resident Microsoft Project source plans at: Creating Project Views from Server Resident Project Plans for OnePager Pro (Portal) .

3) As with Microsoft Project IMS source plans and separate multiple Microsoft Project source plans, the instructions provided in this article for single Microsoft Project source plans with respect to the OPP modes of NEW, UPDATE, and OPEN apply to import from server resident Microsoft Project source plans.

Using Enterprise Custom Fields from Microsoft Project Source Plans in Conditional Import Filters Rules

1) A complete discussion of Enterprise Custom Fields is provided in this article: Using Enterprise Custom Fields from Microsoft Project 24.3.1-60.

2) As discussed above in the previous sub-sections of this article, once a Microsoft Project source plan or package are provided to OPP regardless of media (i.e., desktop or server resident), OPP can determine which source plan rows to import based on either the flag field you designate or the fields and logic you create in the Conditional Import Rules form. However, it is required that you must first assure that any set of Enterprise Custom Fields you wish to use (for any purpose in OPP) be first included as described in the article referenced in the previous paragraph.

3) Again, as discussed in the previous sub-sections, with respect to the OPP modes of NEW, UPDATE, and OPEN apply to import rules using Enterprise Custom Fields.

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

(7.18.1.2-60)‏‎