Multi-level group by using a hierarchical outline code?

[anovak]

OK, I have a multi-level outline code that pretty much the Performer
"portfolio"


Institution.VicePres.DeptHead.GrpMgr.Team

Fair enough? Now, the PWA appears to auto-rollup dollar figures
(e.g., Budget Cost and Cost respectively) at the level you are
grouping by. That's great. However...

If you want to give users the ability to see rolled up values by
either:

Institution.
Institution.VicePres
Institution.VicePres.DeptHead
Institution.VicePres.DeptHead.GrpMgr

Would I have to create 4 more Performer type custom fields
(Institution_Performer,VicePres_Perfomer,DeptHead_Performer,GrpMgr_Performer,
etc.) and require the end user to fill in each one of those when they
create the initial Project or can you somehow specify 1st level, 2nd
level, etc?

Would it be better to just create 4 separate and distinct Portfolio
fields than to have one hierarchical one? Seems to me it would be
more trouble to the end user and I imagine it would be difficult to
syncronize each field to where if you select, say Institution A, the
VPs for Institution A would then appear in the VicePres_Performer
field.

I may be just going off in a direction I shouldn't have to but I'd
really appreciate some advice about this and exactly what technique
should be used to allow for multi-level grouping (high-to-low).

Thanks,
Andy Novak
UNT

 

[mike.mahoney]

OK, I have a multi-level outline code that pretty much the Performer
"portfolio"

Institution.VicePres.DeptHead.GrpMgr.Team

Fair enough? Now, the PWA appears to auto-rollup dollar figures
(e.g., Budget Cost and Cost respectively) at the level you are
grouping by. That's great. However...

If you want to give users the ability to see rolled up values by
either:

Institution.
Institution.VicePres
Institution.VicePres.DeptHead
Institution.VicePres.DeptHead.GrpMgr

Would I have to create 4 more Performer type custom fields
(Institution_Performer,VicePres_Perfomer,DeptHead_Performer,GrpMgr_Performe­r,
etc.) and require the end user to fill in each one of those when they
create the initial Project or can you somehow specify 1st level, 2nd
level, etc?

Would it be better to just create 4 separate and distinct Portfolio
fields than to have one hierarchical one? Seems to me it would be
more trouble to the end user and I imagine it would be difficult to
syncronize each field to where if you select, say Institution A, the
VPs for Institution A would then appear in the VicePres_Performer
field.

I may be just going off in a direction I shouldn't have to but I'd
really appreciate some advice about this and exactly what technique
should be used to allow for multi-level grouping (high-to-low).

Thanks,
Andy Novak
UNT

Andy

PWA 2003 did this perfectly well but PWA 2007 does not. Consequently
I tend to avoid hierarchical codes (Note they still work in Data
Analysis).

regards

Mike

 

[anovak]

Andy

PWA 2003 did this perfectly well but PWA 2007 does not. Consequently
I tend to avoid hierarchical codes (Note they still work in Data
Analysis).

regards

Mike

Mike, in what way does PWA 2007 not do well with hierarchical codes?

 

[mike.mahoney]

Mike, in what way does PWA 2007 not do well with hierarchical codes?- Hide quoted text -

- Show quoted text -

Sorry for the slow response. There are at least two issues: The first
is generally recognised bug where the project information box in MSP
loses data. This is more of o problem with a hierarchical code. The
second is that in PWA in 2003 when you grouped on a hierarchical code
it would indent on each level of the code, generate a summary and also
output the code description rather than the code itself. To replicate
(at least the summary and indentation) you have to have a number of
"flat"codes.

regards

Mike

 

[anovak]

Sorry for the slow response. There are at least two issues: The first
is generally recognised bug where the project information box in MSP
loses data. This is more of o problem with a hierarchical code. The
second is that in PWA in 2003 when you grouped on a hierarchical code
it would indent on each level of the code, generate a summary and also
output the code description rather than the code itself. To replicate
(at least the summary and indentation) you have to have a number of
"flat"codes.

regards

Mike

Mike, is the hierarchical indention problem by design or is this a bug
as well? My gut tells me its a bug.

Thanks,
Andy Novak
UNT

 

[mike.mahoney]

Mike, is the hierarchical indention problem by design or is this a bug
as well? My gut tells me its a bug.

Thanks,
Andy Novak
UNT- Hide quoted text -

- Show quoted text -

Andy

Its clearly an oversight on Microsoft's part. They have failed to
migrate this funcionality into PWA 2007 control, and it has a
signicant effect on configuring in 2007. Multilevel structures
greatly improve usability but if you cannot collapse and expand them
in reports their value diminishes considerably.

regards

Mike

 

[anovak]

Andy

Its clearly an oversight on Microsoft's part. They have failed to
migrate this funcionality into PWA 2007 control, and it has a
signicant effect on configuring in 2007. Multilevel structures
greatly improve usability but if you cannot collapse and expand them
in reports their value diminishes considerably.

regards

Mike

I wonder if Microsoft is aware of this issue and is intending to fix
it?

How about OLAP and the Data Analysis views? Are the "outline codes"
collapse and expand for reporting in this area?

 

[mike.mahoney]

I wonder if Microsoft is aware of this issue and is intending to fix
it?

How about OLAP and the Data Analysis views? Are the "outline codes"
collapse and expand for reporting in this area?- Hide quoted text -

- Show quoted text -

Andy

Can't comment on Microsoft, but there has been enough discussion on
this topic.

Data Analysis reports behave as expected.

Mike

 

[anovak]

Andy

Can't comment on Microsoft, but there has been enough discussion on
this topic.

Data Analysis reports behave as expected.

Mike

Is there a hotfix for this indention problem at this juncture or is it
not looked upon as an issue?