how to create analytic chart report that shows Area wise issue and Risk count RRS feed

  • Question

  • Hi everyone

    I am using project server 2010,and having Area(Project Type) of Custom field

    I want to create a Analytic Chart Report that shows Area wise issue and risk count

    scenario is issues and risks are associated with project and project is associated with Area 

    problem which i am facing is that

    when i place the Dimension Area_Project in Bottom axis  and Measure issue count in Series,

    it is showing sum of all issues that are associated with every project in All Areas

    suppose there are 2 issues associated with Project P1,and 3 issues are associated with Project P2,Project P1 is associated with Area 'carbon plant' and Project P2 is associated with the area 'Energy'

    Result which i am getting is for every Area(i.e Carbon plant,energy)   issue count as 5(sum of all issues),which is wrong,Carbon plant shoud show Issue count as 3 and energy as 2

    if anyone has any idea,plz let me know

    • Edited by anuj astro Wednesday, March 6, 2013 8:00 AM
    Wednesday, March 6, 2013 7:57 AM

All replies

  • Do you have any hierarchies defined around your dimension? or if hierarchy makes sense in your scenario like [Area - Project - Issue].

    If you are using a OLAP cube, you can use cube browser to see if the relations you are looking for exist.

    When you drag a dimension on a chart it is rolled up to 'All', have you tried filtering the axis to verify results?

    Another option can be to connect your cube with Excel and create a chart there for verification.

    Wednesday, March 6, 2013 4:11 PM
  • hi umair

    i have tried in excel also,it is showing the same result,i am doubtful whether this hierarchy exists or not, i am not aware of cube browser as i am pretty new to performance point services

    i have pasted the query below,see if you can help it

    HIERARCHIZE( { [Area_Project].[Area_Project].DEFAULTMEMBER, [Area_Project].[Area_Project].[Area_Project].&[{241C6A78-3B0C-462C-A538-3F25BA4886A6}], [Area_Project].[Area_Project].[Area_Project].&[{46AF4387-2B32-4275-9A65-9F91A263D9C9}], [Area_Project].[Area_Project].[Area_Project].&[{E21966B8-4E6D-4203-B1B5-771D22F56369}], [Area_Project].[Area_Project].[Area_Project].&[{86A8F321-D490-47E9-9161-BE67B2C0D477}], [Area_Project].[Area_Project].[Area_Project].&[{CC3EE4B6-8CFB-46E7-ABFD-573861127D96}], [Area_Project].[Area_Project].[Area_Project].&[{E1A68F6D-112A-49A6-8C3E-7C5773134278}], [Area_Project].[Area_Project].[Area_Project].&[{07831CB9-A89A-4F3E-B238-C813C4E90CEC}] } )

    { [Measures].[Issue Count] }

    FROM [MSP_Project_SharePoint]


    Thursday, March 7, 2013 7:38 AM
  • I would say the issue lies in your data model and how your fact table is designed.

    To see if hierarchy exists, from your PPS report [Area_Project] axis, what list of values do you see under it. Is it a flat list of all Areas and Projects or a tree view?

    Thursday, March 7, 2013 4:18 PM