Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only

  • 1.  Changing level names - documentation deficiency

    Posted 03/05/23 11:46 AM

    PAW 2.0.84

    The documentation states that we can changes the default names of hierarchy levels into meaningful names.

    However, one should create a TI process containing: RefreshMdxHierarchy( '' ); to see the effect when the process has run.

    https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=2084-rename-hierarchy-levels-in-dimension-editor



    ------------------------------
    Wim Gielis
    ------------------------------


  • 2.  RE: Changing level names - documentation deficiency

    Posted 03/05/23 11:53 AM

    You are right Wim, without running the refresh, you cannot use the names. Should be in the documentation as it is not clear on how to update or apply these.


    Another short-coming is the ability to apply names on hierarchies other than the default.

    With developers using hierarchies more and more, this looks to be an oversight in the engine.



    ------------------------------
    George Tonkin
    Business Partner
    MCI Consultants
    Johannesburg
    ------------------------------



  • 3.  RE: Changing level names - documentation deficiency

    Posted 03/05/23 10:51 PM

    And also, whether the string length limit that used to apply before to named levels also applies now must also be added to the documentation.

    Using Named Hierarchy Levels with TM1 Dimensions - IBM Documentation



    ------------------------------
    Amin Mohammed
    ------------------------------

    Original Message


  • 4.  RE: Changing level names - documentation deficiency

    Posted 03/06/23 10:33 AM

    This works fine in most versions. The implementation is strange, but it works. Instead of using the hierarchies dimension, they added hierarchies as members of the }dimensions dimension



    ------------------------------
    Ryan Clapp
    ------------------------------

    Original Message


  • 5.  RE: Changing level names - documentation deficiency

    Posted 03/05/23 09:28 PM

    As my best practice, I have a process TM1.Dim.Finalize, which I call from each dimension update process to update system subsets, attributes, formats, etc.

    On the Epilog of that process I call:

    DimensionUpdateDirect( dim );
    RefreshMDXHierarchy( dim );

    Which updates the hierarchy level names and compacts the dimension



    ------------------------------
    Vlad Didenko
    Founder at Succeedium
    TeamOne Google Sheets add-on for IBM Planning Analytics / TM1
    https://succeedium.com/teamone/
    ------------------------------



  • 6.  RE: Changing level names - documentation deficiency

    Posted 03/13/23 06:44 PM

    Hi Wim and Amin, 

    We do have this process running for you autoamticaly upon the level naming, you'd just need to refresh the database tree to see your level name changes available.

    We'd add this note as well as the naming limitation to 255 characters.

    Thank you all for the feedback!

    Best Regards,



    ------------------------------
    Svetlana Pestsova
    IBM Planning Analytics Product Manager
    ------------------------------

    Original Message


  • 7.  RE: Changing level names - documentation deficiency

    Posted 04/01/23 08:22 AM

    Thanks, I saw it in the session a couple of days ago.



    ------------------------------
    Wim Gielis
    ------------------------------

    Original Message


Related Content