We recently updated our recorded demonstration to include the features and controls in our latest version, 6.0. If you have folks in your organization who are interested in OnePager, this is one of the best ways to do that:

If you’d prefer to have us show up to a team meeting and give a private live demonstration, please let us know by sending an email to learning@onepager.com with your request. We’d be happy to accommodate that.

Have other videos that you wish we’d create? Please send us your ideas and we’ll get on it!

Our final installment in the review of what’s new in OnePager 6.0 covers new flexibility in the unique ID field for Microsoft Project and Project Server. OnePager Pro has traditionally used the Microsoft Project Unique ID or the Project Server/Project Online GUID to uniquely identify tasks in your report. Unique IDs help streamline updates, preserve custom formatting, and a lot more.

While most OnePager Pro users have done just fine with the default Unique ID or GUID options, some more advanced users have needed more flexibility to define a custom field for their unique IDs. OnePager Pro now lets users select any text field as a unique ID.

We’re continuing our look at the new OnePager 6.0. So far, we have explored additional text columns and custom import filters. This week, we will look at unlimited field mappings. While this particular upgrade may not have as much pizazz as the previous two, we anticipate that it will save users hours and hours of time.

If you have used OnePager for a while, you know that OnePager imports a select set of fields from Microsoft Project or Excel. While users have always been able to use their templates to control which fields are imported, OnePager had not previously given users a way to retroactively add a field to a project view, if that field wasn’t imported when the report was first created. Beginning with OnePager 6.0, users can add an unlimited number of custom fields into an existing OnePager report, even if those fields didn’t exist when the report was first created.

Last week, we kicked off our release of OnePager 6.0 with an overview of additional text columns. This week, we’ll continue our discussion with a look at OnePager’s new custom filtering option.

If you’ve used OnePager for a while, you know that you can use a flag field (e.g. Flag20) to decide which tasks and milestones will be included in your report. Custom import filters take this a step further by allowing you to define rules to drive which items will be in your report. This means that you can build a OnePager report for all tasks scheduled to start in May that are assigned to your engineering team, without actually having to locate those tasks in Project or Excel first.

Over the next few weeks, we’ll be publishing a series of articles that cover the major highlights of our new OnePager 6.0 release. As with all OnePager releases, we’ve made hundreds of improvements–both big and small–but this series will focus on the major themes that are most important to our customers.

The first major upgrade in OnePager 6.0 is the ability to display multiple columns of text in your report. In previous versions of OnePager, users could incorporate text in their Gantt charts through the use of one swimlane column and one “row label.” We are expanding the latter category and renaming it “text columns,” allowing for an expansion to five custom text columns, plus the swimlane column, for a total of six: