change order of hierarchy levels in dimensions

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • change order of hierarchy levels in dimensions

    Hello,

    I'm new to Palo and it's not clear for me which are the best practices for some issues regarding dimension levels, hierarchy, consolidation, etc. in Palo.

    I have a dimension with the following hierarchy levels:

    1. Level: Vertriebsbereich
    2. Level: Innendienst/Außendienst
    3. Level: Firmennummer
    4. Level: Betreuernummer

    Now I want to analyze/konsolidate this dimension in another order, i.e.:

    1. Level: Innendienst/Außendienst
    2. Level: Betreuernummer
    3. Level: Firmennummer

    Do I have to create a dimension for each sort of constellation?
    Would it be better to use dimension subsets?
    Will the aggregations/consiólidations still work in a dimension subset?
    How can I achive this and which are the best practices for this issue?
    I need to get the "correct path" here, since these level changes are a very common issue.

    Thanks and best regards,
    KM
  • hi konrad

    you can have different hierarchies in a dimension. so you could have one element called "hierarchy one"with childs being

    1. Level: Vertriebsbereich
    2. Level: Innendienst/Außendienst
    3. Level: Firmennummer
    4. Level: Betreuernumme

    and another element being "hierarchy two" having childs being

    1. Level: Innendienst/Außendienst
    2. Level: Betreuernummer
    3. Level: Firmennummer


    This way, when you pate view, you select one of the two hierarchies with all its childs,,,

    hope it helps...
    _____________
    Windows 8.1
    Office 2010
    Google Chrome
  • Thanks for your reply!

    So for each hierarchy I create a TreeFH with a corresponding prefix on the element names (i.e. "H1_" = hierarchy one, "H2_" = hierarchy two, etc.) and in the second step I merge all corresponding hierarchies in a TreeJoin. And this TreeJoin will be the content of the dimension. I think I need this prefix in order to get unique element names. So I have only one dimension with different hierarchy levels and different orders.

    Is this the right way?

    BR,
    Konrad
  • Hallo Konrad,

    actually yes, this is the right way, but in fact you do not need to prefix the base elements with the prefix (only the consolidated ones)

    use TreeFH or TreePC to create hierarchies, depending on what is the format of your input data, and TreeJoin to assemble them in one single dimension

    regards
    laloune

    Post hoc, non est propter hoc