Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

Help with displaying Hierarchy data

Hello

 

Any ideas on displaying the hierarchy of data  present in image 1 (excel sheet) in Power BI similar to hierarchy that appears in image 2. 

 

My Data to be used in Power BISample image how hierarchy to be dispalyed

 

  • Anonymous,

     

    Your cost center's need to be unique.

     

    I create the following in the query editor:

     

    with this little chunk of code:

     

    // This should match the diagram

    #table(
    type table
    [
    #"NodeKey" = Int64.Type,
    #"CostCenter" = text,
    #"ParentKey" = Int64.Type
    ],
    {
    { 1, "CPS", null },
    { 2, "CPS_ADMIN", 1 },
    { 3, "IC", 1 },
    { 4, "ICO", 3 },
    { 5, "PBS", 1 },
    { 6, "PBS_ENG", 7 },
    { 7, "PBS_ENG_F", 5},
    { 8, "PBS_ENG_LA", 5},
    { 9, "PBS_MKT_F", 1}
    }
    )

    // I wrote this before looking at the diagram, only looked at your table
    #table( type table [ #"NodeKey" = Int64.Type, #"CostCenter" = text, #"ParentKey" = Int64.Type ], { { 1, "CPS", 1 }, { 2, "CPS_ADMIN", 1 }, { 3, "IC", 1 }, { 4, "ICO", 1 }, { 5, "PBS", 3 }, { 6, "PBS_ENG", null}, { 7, "PBS_ENG_F", 5}, { 8, "PBS_ENG_LA", 5}, { 9, "PBS_MKT_F", 3} } )

    You could probably use the text but I the example shows numbers (whole numbers).

     

    I then followed the rest of the example at https://www.daxpatterns.com/parent-child-hierarchies/ making all the Calculated Columns and Measures, made up a small 'Expense' table and then visualized in a Matrix:

    *edited the picture for the new Query Editor table above.

     

     

    NodeKeyExpense
    110
    220
    330
    490
    580
    650
    740
    810
    9 

     

    Maybe this example will not work for your current issue but it's possible that some of the concepts might aid you in creating what you hope for.

5 Replies

    • Anonymous's avatar
      Anonymous
      Not applicable

      The below is the only data I have in source which is just 13 rows all together. However when I try using Path Function, the error I get shows CPS_Admin has multiple values where it is not. Can anyone help me understand how to resolve this error.

       

       

       

      • ChrisMendoza's avatar
        ChrisMendoza
        Resident Rockstar

        Anonymous,

         

        Your cost center's need to be unique.

         

        I create the following in the query editor:

         

        with this little chunk of code:

         

        // This should match the diagram

        #table(
        type table
        [
        #"NodeKey" = Int64.Type,
        #"CostCenter" = text,
        #"ParentKey" = Int64.Type
        ],
        {
        { 1, "CPS", null },
        { 2, "CPS_ADMIN", 1 },
        { 3, "IC", 1 },
        { 4, "ICO", 3 },
        { 5, "PBS", 1 },
        { 6, "PBS_ENG", 7 },
        { 7, "PBS_ENG_F", 5},
        { 8, "PBS_ENG_LA", 5},
        { 9, "PBS_MKT_F", 1}
        }
        )

        // I wrote this before looking at the diagram, only looked at your table
        #table( type table [ #"NodeKey" = Int64.Type, #"CostCenter" = text, #"ParentKey" = Int64.Type ], { { 1, "CPS", 1 }, { 2, "CPS_ADMIN", 1 }, { 3, "IC", 1 }, { 4, "ICO", 1 }, { 5, "PBS", 3 }, { 6, "PBS_ENG", null}, { 7, "PBS_ENG_F", 5}, { 8, "PBS_ENG_LA", 5}, { 9, "PBS_MKT_F", 3} } )

        You could probably use the text but I the example shows numbers (whole numbers).

         

        I then followed the rest of the example at https://www.daxpatterns.com/parent-child-hierarchies/ making all the Calculated Columns and Measures, made up a small 'Expense' table and then visualized in a Matrix:

        *edited the picture for the new Query Editor table above.

         

         

        NodeKeyExpense
        110
        220
        330
        490
        580
        650
        740
        810
        9 

         

        Maybe this example will not work for your current issue but it's possible that some of the concepts might aid you in creating what you hope for.