Grouping Levels in Project Center View

N

Neels

Hi,

How can I add one more level of Grouping in my Project Center View?
Currently 3 levels are supported within the Project Server.
This is required to be done as I have a hierarchial structure onto which I
want to map the Projects by Grouping them accordingly.

Thanks a lot in advance.

Regards,
Neel
 
S

supercoolmanchu123

Nor do I. But I am very intriguied. When I go to Server Setting |
Grouping Formats, i can set formatting for 4 levels. Yes, 4.

But when setting grouping in Project Center, or defining the default
group for a view, there are only 3.

Is this just an oversight? Or am I missing where that 4th group is
applied?

Also note that the Project Outline Structure (indenting), is retain
AFTER the grouping. This is not how Proj Pro works. In Proj Pro, the
Outline Structure, or indenting, is ignored in the grouping (unless
you specifically ask for it).

Anyone figure out how to tell PWA 2007 to ignore the indenting, just
like Project Pro 2007 works?
 
N

Neels

Precisely, If there is a 4th Level Grouping format settings, then there
should be a round-about way of getting this done.

Is this problem resolved in PWA2007?

Additionally, Can I create a customised view with an external Database
Procedure to get this done?

Any thoughts???
 
S

supercoolmanchu123

Not resolved in PWA2007 as far as I can tell. That's the platform I am
working on. Not sure if you can use an external data procedure to get
this done. Can you share a little more about your approach, and maybe
I can help?

Any thoughts on how to ignore indenting/outlining in the PWA 2007
Views?

At this point, we are seriously considering requiring users to refrain
from indenting entirely. All of our 'views' will be based on Groups.
Of course, if we are stuck with 3 on in PWA, that;s going to be
problem. Our standard, cross functional WBS has 6 levels... We will
also develop macros so our users can enter new tasks while in Group
View in ProjPro2007.

Any other issues you can suggest we might have by not using the
Outlining feature?

Thanks!!
 
M

mike.mahoney

Not resolved in PWA2007 as far as I can tell. That's the platform I am
working on. Not sure if you can use an external data procedure to get
this done. Can you share a little more about your approach, and maybe
I can help?

Any thoughts on how to ignore indenting/outlining in the PWA 2007
Views?

At this point, we are seriously considering requiring users to refrain
from indenting entirely. All of our 'views' will be based on Groups.
Of course, if we are stuck with 3 on in PWA, that;s going to be
problem. Our standard, cross functional WBS has 6 levels... We will
also develop macros so our users can enter new tasks while in Group
View in ProjPro2007.

Any other issues you can suggest we might have by not using the
Outlining feature?

Thanks!!








- Show quoted text -
Click to expand...

Neel

I submitted this observation in a separate thread

Formatting aside indenting based on a hierarchical code seem to have
eliminated in PWA 2007. A significant benefit of a
hierarchical code - rolling up and collapsing to the parent level is
no longer possible.
This fundementally changes coding strategy. You now need 2 or more
codes to achieve
results you could get in 2003 with a structured code.

In project center or resource center (RBS is a good example) there is
no automatic indentation or summarisation based on hierarchy when you
group on this field.

Regards

Mike
 
S

supercoolmanchu123

Indenting based on hierarchical Outline Codes also seems to have been
eliminated in ProjectPro 2007.

This seems pretty loopy to me. I am having a hard time trying to
figure out how MS justified this change. So hard in fact, i am left to
believe that its a mistake.

Any word if MS will re-instate this core functionality into ProjPro
2007, PWS 2007?

Thanks
 
G

Gary L. Chefetz [MVP]

Are we all talking the same language here? Grouping formats repeat
themselves once applied. So, if you apply a grouping format and group by a
hierarchy that has more than four levels, then the pattern repeats. Grouping
formats have nothing to do with how many fields you can group by.

--


Gary L. Chefetz, MVP
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
For Project Server Books: http://www.projectserverbooks.com
For Project Server Training: http://www.projectservertraining.com
For Project FAQS: http://www.mvps.org/project
 
M

mike.mahoney

Are we all talking the same language here? Grouping formats repeat
themselves once applied. So, if you apply a grouping format and group by a
hierarchy that has more than four levels, then the pattern repeats. Grouping
formats have nothing to do with how many fields you can group by.

--

Gary L. Chefetz, MVP
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com
For Project Server Books:http://www.projectserverbooks.com
For Project Server Training:http://www.projectservertraining.com
For Project FAQS:http://www.mvps.org/project










- Show quoted text -
Click to expand...

Gary

There are two separate issues
In 2003 group banding applied to each level of a hiearchical code,
therefore a 4 level code would have 3 indentations and 4 colour bands.
In 2007 there are no indentations and only one colour band
(effectively a flat code).
Therefore if you all codes in 2007 are flat and you can only have 3
groupings in a report, the 4th level format option is redundant.
Am I sounding really nerdy (geeky - us speak)?

regards

Mike
 
S

supercoolmanchu123

Maybe a little geeky, but you have described the issue exactly.

We are on RTM actually. I am hoping this is fixed in the real
release??? Please say yes??

Anyone figure out how to NOT group by Project and Summary Tasks AFTER
applying the group?

So annoying... I heard from someone there was a checkbox in 2003 to
turn this on or off (just like in ProjPro).

Thanks.
 
Top