MS Project Grouping Functionality doesn't work properly

Question

Hello,

I've been running tests in MS Project to convert P6 schedules over to Project and found that the grouping functionality in Project doesn't hold from task view to task view.  Knowing there's a server delay, I've waited to refresh the database, which isn't even a visible command on the out-of-the-box ribbon, and still had the same issue.  Has anyone else experienced this?

Thanks in advance,

Doug L.

Answer 1

Everyone thank you so much for replying!

@Dale Howard - I will use the summary tasks and see if that helps.  Thank you very much for the information. 

@Tom_BPC - I know that question was confusing and my apologies.  Basically, what i saw within the view after I reverted back to it was summary level tasking for each of my WBS elements directly above the tasks, as if i had a split view of summary tasking vs detailed tasking.  I did not make any other changes to the view, rather it appeared automatically.  I felt this was a table and metadata issue but wasn't sure so I wanted to reach out.

Thank you again,

Doug L.

Answer 2

Doug,

After reading it 4 times, I still don't understand what you mean by, " ... then come back to it and I get summary level tasking directly above my first dataset or WBS level."  In the absence of a specific screenshot or problem description, I'd suspect that a change to the view has been made inadvertently, maybe in the filter.  

Where P6 is protective of saved Layouts (explicitly suggesting a save whenever a new Layout is opened and discarding any unsaved changes), Project has a bias in the opposite direction.  Project silently accepts (and saves in memory) any changes you make to the current view - including filter, table, group, and screen (and, in recent versions at least, Sort and Outline).  If you make some changes to an existing view and then save it with a new name, the original view remains changed.  The changes are made permanent when you later save the file, even if you have changed to a different view.  In Project, therefore, some experienced users make a habit of segregating the views used for schedule creation and analysis from those used for reporting, being careful never to modify the latter.

Good luck, tom

Answer 3

Doug --

This is where Microsoft Project and Primavera parts ways.  Primavera organizes tasks into groups using grouping.  Microsoft Project organizes tasks using summary tasks.  If you replace your grouping with summary tasks in Microsoft Project, this will take care of your problem.  Hope this helps.

Answer 4

I understand, but just to be clear, saving a layout view in Projects will not automatically hold the grouping, filtering, ect. as it does within Primavera?  I'm going to be reaching activity levels of up to 10K+. I save a view, switch that view, then come back to it and I get summary level tasking directly above my first dataset or WBS level.  Why does the software do this when I didn't ask it to?

Answer 5

Doug --

Grouping is an attribute of the View in which you apply the Group.  This is because the definition of a View in Microsoft Project is as follows:

View = Table + Filter + Group + Screen

This means if you want the same Group applied in every task View, you will need to apply that Group manually to each View.  Hope this helps.