Follow

What are the common problems associated with MSP and how can I fix them?

PPO's bi-directional integration with MSP allows for data to be transferred quickly and easily from MSP to PPO and back to MSP. However, as with any integration, there are some basic problems or errors that present themselves from time to time. This article covers the five most common errors associated with MSP and explains how to resolve them:

Resources are mapped incorrectly

Background

PPO’s Employees entity maintains a pool of resources that are used by PPO users to allocate Issues, Risks and Tasks. When Microsoft Project (MSP) is used for project planning and the project plan is then imported into PPO, resources recorded in MSP are not automatically imported into PPO as MSP has its own resource pool. However, if PPO’s MSP Add-In is used to synchronise the resources in MSP with the employees in PPO and the resources field is mapped in PPO's System Configuration, then resources can be imported automatically with the user's project plan,  using the Import Tasks Wizard (for detailed steps on how to sync resources, see the following FAQ)

The result of syncing resources in MSP is that every resource is awarded a phonetics key:

mceclip0.png

This key corresponds with the employee's key in PPO:

mceclip1.png

The problem

The resources are not imported because PPO cannot find an exact match for the resources that are being imported and therefore cannot assign the resource to the applicable task.

mceclip3.png

The fix

To resolve the problem, open MSP and connect to the MSP add-in, ensure the current instance's URL is provided when connecting, and then import the resources again from the Import resources tab.

mceclip2.png

The employees will be updated, showing the correct employee key and the next import should be successful.

 

Project plan is too big

The problem

PPO has a 50MB upload limit per document - the same rule applies to project plans. If a project plan is uploaded that is bigger than 50MB, a time-out error or the following error message will appear:

mceclip11.png

The fix

The following two methods can be employed to reduce the file size:

1. The MSP file can be compressed to a zipped folder and the zipped folder can then be imported into PPO. The size of the zipped folder will need to be under 50MB to import successfully.

mceclip5.png

2. MSP accumulates data as and how the users add lines, baseline schedules, update progress and perform other updates on the plan. All the history of all the changes made to the MSP plan is stored within the plan itself, increasing its file size. It often helps to copy the whole project plan over into a new MSP document to clear it of all history. This should reduce the MSP's file size and the new document can then be imported into PPO.

 

No tasks are being imported

The problem

Often when a project plan is imported, no tasks are uploaded:

mceclip8.png

The fix

This problem can occur due to:

All the tasks have already been completed, are all marked as 100% and are therefore being filtered out by the global filter.

The way to check this is to go to the Task List page and disable the tasks global filter. If the reason why no tasks are showing is indeed because of the tasks global filter, the tasks should all appear once the global filter has been disabled.

mceclip9.png

 

Progress in MSP does not correspond with progress in PPO

Background

PPO shows the total actual progress percentage and the total planned progress percentage on the project entity.

mceclip13.png

These values are calculated based on the information contained in the tasks entity. The values are not being imported from PPO, which allows users who import plans via Excel or captures them directly on PPO, to also make use of planned and actual progress calculations.

 

The problem

The problem is, however, that the total progress percentage as calculated by PPO does not always match up to the planned progress percentage calculated by MSP (for more details on how to set up planned progress percentage in MSP, see the following FAQ).

mceclip14.png

The fix

The reason why these values may differ is based on the different ways in which planned progress percentage is calculated.

In PPO, only the tasks where the Task Type is "Task" are taken into account for the planned progress percentage calculation. All project tasks, summary tasks, and milestones are excluded from the calculation by default. However, in MSP, all tasks AND milestones that have a duration will be taken into account for the planned progress percentage calculation. Thus, if a milestone is awarded a duration, this duration will also be taken into account.

The first thing to look for, then, is whether the MSP plan contains any milestones that have a duration awarded to them:

mceclip15.png

A milestone, by definition, is a point in time - it should not have a duration. If all the milestones in MSP are updated to 0 days duration, the planned progress percentage on MSP and on PPO should correspond.

If, however, the values still don't correspond, it may be because there are more tasks on PPO (some of them filtered out by the global filter), than there are in MSP. If more tasks exist on PPO, then the project's total duration, as calculated by PPO, will be greater, therefore affecting the planned progress percentage calculation.

To check this, go to the task list on the project and disable the tasks global filter. Check whether the number of tasks on the task list correspond with the number of line items in MSP (remember that the Project Task is shown on Line 0, so there may be a 1 task difference). If more tasks exist on PPO than on MSP, the additional tasks must either be added to MSP and marked as 100% actual progress, or they must be deleted from PPO.

mceclip12.png
Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request
Article is closed for comments.
Start a 30 Day Free TrialClick ClickNo Credit Card and No Obligation
Powered by Zendesk