Difference between revisions of "Conditional Import for Version 6.0 (Portal)"

Revision as of 20:38, 9 November 2016

Overview

Versions of OnePager Pro and Express prior to 6.0 required you to insert a column (i.e., flag columns) into your plan source file that tells OnePager which rows to import. These flag columns for Microsoft Project plan source files were typically columns named Flag1 through Flag20. OnePager Pro (OPP) used these flag columns to control the import of rows. In both OnePager Pro and Express (OPX) you could use Numeric columns or Boolean columns as long as the contents were 1’s to indicate Yes (bring in this row) or 0’s to indicate No (do not import this row).

This approach to controlling the import of Microsoft Project/Excel plan source file rows is quite flexible. However, it required a modification to the plan source file before import to OnePager so you can limit the rows presented in the resulting project view.

The articles in this Conditional Import series will explain how you can use Conditional Import to simplify the import of data into OnePager and increase your flexibility when preparing project views to support project schedule conversations and presentations.

Upfront Links to Conditional Import Detailed Articles

For those of you who would like to get started right away in mastering Conditional Import at a more detailed level, the links immediately below will take you to the information. If you first would like to see some examples of how Conditional Import can be used, please read the material beyond the links below:

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

(7.18.1-60)‏‎