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

From OnePager Documentation
Jump to: navigation, search
(Overview)
(Overview)
Line 1: Line 1:
 
==Overview==
 
==Overview==
  
Versions of OnePager Pro and Express '''prior''' to 6.0 required you to use a '''field''' (i.e., '''flag''' field) into your Microsoft Project or Microsoft Excel '''source plan''' that tells OnePager which rows to import. These '''flag''' fields for  '''source plans''' were typically fields named '''Flag1 through Flag20''' for Microsoft Project or some '''Boolean''' field for Microsoft Excel.  OnePager Pro ('''OPP''') used these '''flag''' fields to control the import of rows.  In both OnePager Pro and Express ('''OPX''') you can use '''Numeric''' fields or '''Boolean''' fields 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).  
+
Versions of OnePager Pro and Express '''prior''' to 6.0 required you to use a '''field''' (i.e., '''flag''' field) in your Microsoft Project or Microsoft Excel '''source plan''' that tells OnePager which rows to import. These '''flag''' fields for  '''source plans''' were typically fields named '''Flag1 through Flag20''' for Microsoft Project or some '''Boolean''' field for Microsoft Excel.  OnePager Pro ('''OPP''') used these '''flag''' fields to control the import of rows.  In both OnePager Pro and Express ('''OPX''') you can use '''Numeric''' fields or '''Boolean''' fields 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 for controlling the import of Microsoft Project/Excel '''source plan''' rows is quite flexible.
 
This approach for controlling the import of Microsoft Project/Excel '''source plan''' rows is quite flexible.

Revision as of 19:55, 30 April 2017

Overview

Versions of OnePager Pro and Express prior to 6.0 required you to use a field (i.e., flag field) in your Microsoft Project or Microsoft Excel source plan that tells OnePager which rows to import. These flag fields for source plans were typically fields named Flag1 through Flag20 for Microsoft Project or some Boolean field for Microsoft Excel. OnePager Pro (OPP) used these flag fields to control the import of rows. In both OnePager Pro and Express (OPX) you can use Numeric fields or Boolean fields 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 for controlling the import of Microsoft Project/Excel source plan rows is quite flexible.

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

Links to Conditional Import Detailed Articles

If you first would like to see some examples of how Conditional Import can be used, please read the material at this link: Conditional Import for OnePager .

For those who would like to get started right away using Conditional Import, the links immediately below take you to detailed information:

Conditional Import for OnePager Pro Add-in Conditional Import for OnePager Express Add-in
Conditional Import for OnePager Pro Desktop Conditional Import for OnePager Express Desktop

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)‏‎