Forum Discussion
MS Project: Overallocation not showing in Custom View
Hello,
Thank you for reading this.
I am using Microsoft Project Online Desktop Client MSO (Version 2308 Build 16.0.16731.20542) 64-bit.
It is a Master Project with a Resource Pool. I have created a Custom View based on the Resource Usage view, first by grouping by Resource Name and then by Project (see below screenshot). This provides me with the correct view required, however the overallocation is no longer showing in Red text (as in the default Resource Usage view).
Can someone please guide how can I keep the Custom View AND have overallocations shown in red?
Thank you.
-Vaibhav
11 Replies
There are two aspects of resource overallocations that differ between the default Resource Usage view and the Resource Usage view grouped by resource and project name, which Vaibhav attaches.The first difference is that the Overallocated Resource Name is not shown in red in the grouped view, and the second, also in the grouped view, is that the overallocated work values in the time phase are not shown in red.
For the first question, the Overallocated field serves precisely to identify what you are looking for, which is whether the resource is overallocated.
I have tried by different means to raise this value of Yes, (of course it is associated with the ungrouped resource, and has all its usefulness), to the title of the grouping at the level of the resource name, but it seems like an almost impossible mission.
In my conclusion, the two mentioned formatting characteristics in red are lost when grouping and I do not believe there is a method for them to appear.
Vaibhab, I think that the analysis you are looking for, so necessary and important, of reviewing the over-allocated resources in your different projects, you will have no choice but to do it from the Default Resource Usage view.
However, I give you some suggestions that can help you from the ungrouped view, and that you may already know.
Sort the Resource Usage table by project without grouping.
When you want to hide all assignments and show only the resource names, select the entire table (click on the top left corner), and select hide subtasks(Menú >View > Data > Show Outline > Hide Subtasks), or select the entire table and show all (... All Subtasks).
Insert the Overallocated column to filter overallocated resources.You can include almost all of these options in the quick access toolbar, which will be very useful for this scenario.
Ignacio
- Thank you Ignacio_Martin for your investigation and a workaround.
Someone suggested not to use the Resource Pool to avoid this issue. Do you recommend using a single project file to hold 20+ sub-projects with no resource pool?
Hi VaibhavSapre
As it is a task grouping, I don't think the group title can be displayed in another color if the resource is overallocated.
If it helps, try inserting a logical field, Flag1 for example, whose formula is = [Overallocated], and in the summary and group tasks row select Rollup.
This way at least you have the information of whether the resource is overallocated, even if it is not shown in a different color.Ignacio
Thank you for your reply.
I tried your suggestion but it shows "No", while I know that resource is overloaded for a few months.
- All -- The Overallocated field is entirely useless in this situation because the Overallocated field only displays a Yes value for tasks on which the resource is assigned more work on that task than Microsoft thinks they can do (such as assigning the resource to work 10 hours per day when their Max. Units value indicates they can only work 8 hours per day). The Overallocated field DOES NOT display a Yes value when the resource is overallocated across multiple tasks.
I think the reality is that when grouping is applied in the Resource Usage view, the red text disappears. The approach I uses is NOT using grouping. Instead, I insert the Project column and the Task Summary Name column, which tells me the projects in which the resource is overallocated, and the summary section in which the tasks are located. Just a thought. Hope this additional information helps.
