Problem with percents in Portfolio Analyzer

[Al Himler]

(Proj Server 2003; SQL Server 2005) While creating a Portfolio Analyzer view
that included Resources as a dimension and the number of hours Worked as my
columns across time, I changed the way the Work was displayed from "Normal"
to "Show As"->"Percent of Row Item". The data in the view showed as percents
like I'd expect. I clicked to save the changes and received the feedback
that they had been saved.

I then went back into the view on the Admin screen and saw that the data was
again showing in terms of hours rather than percents. For some reason it
doesn't look like it held the percent setting. Is this is a problem that
anybody else has encountered?

Al

 

[Kathleen]

Hi Al - are you making the change as an administrator in views or are you
making the change at a different permission level? If I change the view as
an Admin I have not had this experience, meaning my settings are pushed out
to the analyzer.

If I make it at another level (in the portfolio analyzer instead of in the
admin portion) then I need to save the view by clicking on "save link" and
then the specific settings are saved on my desktop; however, they are not
retained as a global view.

Hope this helps
K

 

[Al Himler]

Thanks for the reply Kathleen.
I've gone as far as logging directly on to the Project Server box, opening
IE, logging on as Administrator, going to the Admin tab, and then modifying
the Portfolio Analyzer view in there and is still doesn't "take". It looks
fine when I modify the view; then I click to save the changes and it says
that the changes have been saved successfully. But, when I go and modify the
view again and scroll down to the view, it shows the values as number of
hours again rather than percents.

Are you working with the same config of Proj Server 2003 and SQL Server 2005?

Al

 

[Kathleen]

Hi Al - thanks for the info - and also for clarifying the 2005 SQL config - I
missed that in your original post. I am using 2003 SQL so probably can't be
of assistance for you. good luck
k

 

[Al Himler]

For anybody else that runs into this, I found a reference that suggests that
Microsoft did this by design and the way to work around this is to use
calculated fields. See:

http://72.14.205.104/search?q=cache...+"calculated+field"&hl=en&ct=clnk&cd=13&gl=us

Al