Difference between revisions of "Conditional Import for Version 6.0 (Portal)"
| Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
| − | Versions of OnePager Pro and Express '''prior''' to 6.0 required you to insert a | + | Versions of OnePager Pro and Express '''prior''' to 6.0 required you to insert a field (i.e., flag fields) into your source plan that tells OnePager which rows to import. These flag fields for Microsoft Project or Excel source plans were typically fieldss named '''Flag1 through Flag20''' for Microsoft Project and some other '''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 may use '''Numeric''' fieldss or '''Boolean''' fieldss 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 | + | 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 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. | + | 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=== | ===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 | + | 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 that information. 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. |
{| class="wikitable" | {| class="wikitable" | ||
| Line 23: | Line 23: | ||
[[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)]] | + | [[Conditional Formatting for Version 5.3 (Portal) | Conditional Formatting (Portal)]] Repoint this article to Version 6.0 Later |
[[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]] | ||
Revision as of 17:40, 27 December 2016
Overview
Versions of OnePager Pro and Express prior to 6.0 required you to insert a field (i.e., flag fields) into your source plan that tells OnePager which rows to import. These flag fields for Microsoft Project or Excel source plans were typically fieldss named Flag1 through Flag20 for Microsoft Project and some other 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 may use Numeric fieldss or Boolean fieldss 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 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 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
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 that information. 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.
| 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) Repoint this article to Version 6.0 Later
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)
