Ensuring formatting is retained when you create a new project view or snapshot

Sometimes customers will (1) create a new project view from an existing template, or (2) create a new snapshot inside an existing project view, and find that the formatting of the new project view/snapshot is not what they expected. Here is why.

Any time you create or refresh your project view, OnePager looks first to the properties of that project view. Those are the settings saved inside the Project-View Properties form of every project view (and initially inside the Templates menu for every template).

Project-View Properties

All of the changes you've made to your project view that are saved inside the Project-View Properties form will be copied over to the new or refreshed project view when you make it. However, if you make a change to your project view that is not reflected in the Project-View Properties form, then that change will not be copied over to your new project view or snapshot.

For example, let's say we manually change the color of a task bar from green to blue:

Example of mavericking

OnePager will let us do this, but there's no way for it to remember in Project-View Properties that the "Assemble Resources" task should be colored blue. Rather, the data-driven formatting in Project-View Properties says that "Assemble Resources" should be colored green:

Data-driven formatting rule

This brings us to a OnePager best practice: Whenever possible, make formatting changes from the Project-View Properties form, rather than changing the colors/shapes/sizes of task bars and milestones one by one. This will ensure that your formatting is dynamic and will remain accurate even as your project plan changes in the future.