We have become aware of a critically-broken Office Update that Microsoft began pushing to users this past Tuesday, November 12th.
The update, once installed, will immediately break a number of key Microsoft Office features and many Office add-ins, including OnePager. It also will break any third-party applications that rely on certain Office components to be functional on your system.
In short, it is an unmitigated disaster.
To learn how this impacts your use of OnePager, read here to get more details, and to learn how to fix the issue so that your access to OnePager is not interrupted.
For more general information on the issue, since it impacts many other applications beyond OnePager, read here, and here.
In the meantime, if you have not already been hit by this update, please temporarily suspend Office Updates until Microsoft has released a fix. To turn these off, launch Excel, and go to File > Account > Update Options. Choose to Disable Updates
If Microsoft provides us with more information on how to stop this issue from happening without waiting for their next update to be pushed, we will let you know ASAP.
We’d like to remind all of our users, especially those who have been with us for a while, to keep their installations of OnePager current. OnePager interfaces directly with components from Windows, Microsoft Project, Project Online, and Excel. Microsoft periodically makes updates to Windows, Office, and Project, especially if you are using Office 365. If you’re running an outdated version of OnePager, there’s a possibility that you could encounter issues that we’ve already fixed in a later update.
Many IT departments are very good about installing Windows Updates as soon as they come out, and doing the same with Office updates. OnePager isn’t always top-of-mind for them, so we occasionally see cases where the IT department stays on top of updates from Microsoft but forgets to maintain OnePager. This is akin to rotating the tires on your car every 10,000 miles but never changing the oil. The tires will be in great shape, but your engine might end up giving you a nasty surprise!
Most of our Microsoft Project users like having OnePager Pro automatically group swimlanes by one of the outline levels tied to the WBS of the project plan. For example, grouping by Level 1 Summary Name will create swimlanes based on the top-level parent task, whereas grouping by Level 2 Summary name will create swimlanes based on summaries one level lower.
But what happens if your WBS in Microsoft Project isn’t set up so that every outline level matches up to where you’d like to see a swimlane? Take this Microsoft Project plan for example:
Last October, we told you about the non-linear time axis feature of OnePager version 6.1. This new feature allows you to call out a portion of your timeline — making, say, the third quarter of 2019 wider than the second and fourth quarters, so the tasks and milestones from Q3 stand out. OnePager users had been asking for this feature for years, and have been enthusiastic about this new capability.
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.
In our previous post, we covered the ins and outs of unique IDs with Microsoft Project locally on the desktop. This article discusses some of the differences in how unique IDs work when you are using Project Server or Project Online.
When you launch OnePager as an add-in to MS Project, you have the option to connect directly to Project Server/Online or to let MS Project connect to the server and then funnel the information back to OnePager through the desktop client. When you’re using OnePager as a standalone application outside of MS Project, all connections to Project Online and Project Server are direct and do not involve MS Project.
Continuing our earlier discussion of Unique IDs, we’ll turn our attention this week to Microsoft Project. Project generally does a pretty good job of creating and maintaining Unique IDs so that you don’t have to worry about it, but we’ll cover a few gotchas in this article.
Your Unique IDs in OnePager will vary in MS Project based on whether you are:
Using Project on the desktop or connecting directly to Project Online or Project Server over your network; and
Reporting on a single project or on multiple projects
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.