Difference between revisions of "Critical path for OnePager (OnePager Express)"
From OnePager Documentation
(→Critical Path Representation with OnePager Express) |
(→Critical Path Representation with OnePager Express) |
||
| Line 17: | Line 17: | ||
[[Category:Version 5.2]] | [[Category:Version 5.2]] | ||
[[Category:Version 5.3]] | [[Category:Version 5.3]] | ||
| + | [[Category:Version 6.0]] | ||
[[Category:Project Views]] | [[Category:Project Views]] | ||
[[Category:Project-View Properties Form]] | [[Category:Project-View Properties Form]] | ||
Revision as of 14:54, 10 February 2017
Critical Path Representation with OnePager Express
Visualization of a Critical Path is not supported in OnePager Express (OPX).
Where OnePager Pro (OPP) can draw upon calculations made by Microsoft Project with respect to the determination of the critical path, Microsoft Excel does not. Accordingly, OPX does not have the data necessary from a Microsoft Excel import to create critical path visualizations.
As an alternative, in some respects, OPX does support the opening of OPP project views (i.e., OPP .tam files).
- a) When OPX opens a OPX .TAM file where critical path information was previously imported and displayed on task bar visualizations, OPX will support the representation of critical path elements on tasks/milestones and in the specific .TAM file’s legend element.
- b) However, there are no controls provided in OPX for the modification of critical path elements in either the OPX Project-View Properties (PVP) form or in the OPX Template Properties form.
Attempting to perform an UPDATE of a OPP .TAM file with OPX may be problematic and is not recommended.
(10.8)
