Difference between revisions of "Conditional Import for Version 6.0 (Portal)"
(→Overview) |
|||
| Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
| − | Versions of OnePager Pro and Express '''prior''' to 6.0 required you to insert a '''field''' (i.e., '''flag''' field) into your '''source plan''' that tells OnePager which rows to import. These '''flag''' fields for Microsoft Project or Excel '''source plans''' were typically fields named '''Flag1 through Flag20''' for Microsoft Project and 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 | + | Versions of OnePager Pro and Express '''prior''' to 6.0 required you to insert a '''field''' (i.e., '''flag''' field) into your '''source plan''' that tells OnePager which rows to import. These '''flag''' fields for Microsoft Project or Excel '''source plans''' were typically fields named '''Flag1 through Flag20''' for Microsoft Project and 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). |
| − | The approach described above for controlling the import of Microsoft Project/Excel '''source plan''' rows is quite flexible. However, it required a modification to the '''source plan''' before import to OnePager | + | The approach described above for controlling the import of Microsoft Project/Excel '''source plan''' rows is quite flexible. However, it required a modification to the '''source plan''' before import to OnePager. |
The articles in this '''Conditional Import''' series will 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. | The articles in this '''Conditional Import''' series will 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. | ||
| Line 11: | Line 11: | ||
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 Pro/Express Version 6.0 | Conditional Import for OnePager]] 0.4.1.1-60. | 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 Pro/Express Version 6.0 | Conditional Import for OnePager]] 0.4.1.1-60. | ||
| − | For those of you who would like to get started right away in mastering '''Conditional Import''' | + | For those of you who would like to get started right away in mastering '''Conditional Import''', the links immediately below will take you to detailed information: |
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 16:17, 15 March 2017
Overview
Versions of OnePager Pro and Express prior to 6.0 required you to insert a field (i.e., flag field) into your source plan that tells OnePager which rows to import. These flag fields for Microsoft Project or Excel source plans were typically fields named Flag1 through Flag20 for Microsoft Project and 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).
The approach described above for controlling the import of Microsoft Project/Excel source plan rows is quite flexible. However, it required a modification to the source plan before import to OnePager.
The articles in this Conditional Import series will 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.
Upfront 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 0.4.1.1-60.
For those of you who would like to get started right away in mastering Conditional Import, the links immediately below will take you to detailed information:
| Conditional Import for OnePager Pro Add-in 7.18.1.1-60 | Conditional Import for OnePager Pro Desktop 7.18.1.2-60 |
| Conditional Import for OnePager Express Add-in 7.18.2.1-60 | Conditional Import for OnePager Express Desktop 7.18.2.2-60 |
Related Links:
Conditional Formatting (Portal) 11.0.1-60
Using the OnePager "Data" Tab's "Selected file(s)" Button 7.17.1-60
OnePager Express Import of Data from Microsoft Excel 4.4-60
Message to Assist with Setting Import Flags When No Data Are Imported
Understanding Project Views and Snapshots for OnePager Pro 4.1-60
Understanding Project Views and Snapshots for OnePager Express 4.2-60
(7.18.1-60)
