OnePager supports a variety of regional settings for our many customers around the world. This means we will show dates in the local format/language and switch to metric templates that use centimeters instead of inches when appropriate.
In this article, we will show examples of how this works in OnePager by reviewing the scenarios listed below. If you’d like to follow along, go to Control Panel > Region on your device and select each of these options to see how they change OnePager’s display:
If you are a regular user of OnePager Pro with Microsoft Project, you already know about Flag20 and how it’s used to bring over tasks with a Yes value. However, there might be instances where you want to filter your tasks further and exclude tasks once they have finished. When this situation arises, you can use Conditional Import Rules to check not only for Flag20, but also for an incomplete status.
Let’s say we need OnePager to know when a task or milestone finishes so that it can be removed from the chart. Right out of the gate, this sounds like a very tedious task as you would need to not only track the status of each task but also mark them as No in your Flag20 field once they finish. Fear not, though, as there is a much faster and easier way to do this.
In my view, among the many great features of OnePager, none beat Conditional Formatting. With Conditional Formatting, you can create rules to change the color, shape, fill, and other properties of tasks and milestones based on specific rules that you set. However, what happens when you have multiple values to which you need the same rule to apply? You could create a bunch of separate rules, but that’s a lot of work. In this article, we will go over how you can create a conditional formatting rule that tests for multiple conditions at once.
Imagine with me, if you will, that you have a schedule with individual resources assigned to different tasks. Each resource is part of a specific team in your organization, and you would like to be able to color tasks based on the team that the people belong to, not based on their individual names.
If you manage projects in Excel, you’ve probably come across the need to assign tasks to different phases, especially if your project is somewhat complex. There is a right way and a wrong way to set up phases in Excel, and structuring your phases correctly will make it easier to format your charts in OnePager Express.
Many people think that the relationship between a task and a phase in Excel should look like it does in Microsoft Project, with the phase on top, and the tasks indented underneath:
If you’re using OnePager 7.0, you probably know that there is a new set of algorithms that automatically optimize the text in your chart to minimize text collisions.
These algorithms work very well, but every so often, you may find a text collision that sneaks through. In other cases, you might have moved text or shapes around by hand and created a text collision that wasn’t there originally.
If your chart looks good overall, but you have a couple of lingering text collisions, you don’t have to re-optimize your entire chart to fix it. Instead, you can select the pieces of text that are in trouble and re-apply the optimization just to the area of your chart that needs it. In this example, we have three pieces of text that are hard to read. So we can select all three with a Ctrl+Left-Click, and then right-click on any one of the three selections to choose the Re-Optimize Text Collisions option from the context menu:
OnePager will re-run the optimization algorithm only for the selected tasks. So if you’re happy with the layout of the rest of your chart, you don’t have to worry about messing it up while you’re fixing a collision elsewhere.
When creating a chart in OnePager, we want to make sure that the audience knows what the tasks and milestones represent. This is why the labels in a chart are so important.
Most of the time, using the same text field from MS Project will suffice for both your tasks and your milestones, but there are situations where you need to label tasks one way and milestones another. In this article, we are going to discuss how you can import data from two different Microsoft Project fields so that you can use the first field to label your tasks and the second field to label your milestones.
Many users prefer to plan their projects in PPM tools other than Microsoft Project. You might prefer Smartsheet, Primavera P6, Planisware, or some other tool. When using these PPM tools, unique IDs are just as important as they are in Microsoft Project or Excel.
Continuing our series on unique IDs, this week’s post will cover how to correctly establish and maintain a unique ID in an Excel spreadsheet that you are planning to use with OnePager Express. The focus of this article is for project plans that you are building from the ground up in Excel.
If you are using Excel to transfer data from another PPM tool like Planisware, Primavera, or Smartsheet, you’ll want to wait for our next article, which will provide specific instructions for each of those platforms.
When creating a unique ID in Excel, you want to use a field where all the values can be (1) unique and (2) consistent. It doesn’t really matter what you name the field as long as you adhere to these two principles. The unique IDs themselves can be any format that you like. Most users prefer a simple numeric ID, but if you want to create something different, you certainly can.
Whether you are a brand-new OnePager user or someone who’s been with us for a while, you’ve probably seen the concept of Unique ID come up from time to time. If you haven’t stopped to learn about what a Unique ID is and why it is so important, this article is a great place to start.