Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only

  • 1.  Multiselector lists

    Posted Mon January 27, 2025 10:13 AM
    Edited by Ty Cardin Mon January 27, 2025 01:24 PM

    Question:

    I have a dimension with an alternate hierarchy that groups the leaf elements of the base hierarchy.  I want to be able to multi-select parents and return only the children/leaves of the selected parents.  The alternate hierarchy is an attribute hierarchy.

    Not having a problem at all with selecting one parent and returning the children.  However, have not been able to figure out how, or if, the multi-selector can be used to achieve selecting multiple parents and returning all their children.  Or some way to accomplish this.  

    Have done some testing and it does not appear to be feasible to pass to a TI the selections from a Multi-Selector List, but any suggestions would be most welcome.

    UPDATE: Have setup a cube to allow the user to select items and then use those selections in an MDX subset to return the desired subset.  Just not the elegant solution I was looking for.

    ------------------------------
    Ty Cardin
    ------------------------------



  • 2.  RE: Multiselector lists

    Posted Tue January 28, 2025 07:49 AM

    Hi Ty,

    The multiple selection widget generates a set (the set is the members you select in the list) to synchronize to other widgets.  The Advanced synchronization feature can be used on the widget receiving the synchronized set to determine what set to display in the widget based on the synchronized set.  The current options are Set , Set and aggregate, Aggregate and set, and Aggregate. 

    We could extend the Advanced synchronization feature to include 'Children of set' and 'Descendants of set'.  I've also seen one enhancement requests to provide sort options for the set of members that is displayed in the widget.

    The really nice thing about the Advanced synchronization feature is that each widget can do something unique with the set of members that is synchronized to the widget.

     



    ------------------------------
    Stuart King
    Product Manager
    IBM Planning Analytics
    ------------------------------



  • 3.  RE: Multiselector lists

    Posted Tue January 28, 2025 09:50 AM

    Rather than expand the list of options why not add the ability to specify a custom MDX statement with placeholders for the inbound synchronized values.

    (This type of request has been out there since 2017, but seems to constantly be passed over. There are easily 3 or 4 RFEs asking for this type of feature all with their own votes) 



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

    Original Message


  • 4.  RE: Multiselector lists

    Posted Tue January 28, 2025 03:26 PM
    Edited by Ty Cardin Tue January 28, 2025 03:27 PM

    Stuart,

    Thank you for responding.  I finally got a chance to take a look at it again.  I think I understand what you're saying in that using a multi-selector list returns a set to the target item, in this case a cube context dimension.  Yes, if I select two (or three, ...) elements in the selector list, I only have two (or three, ...) elements available in the drop down in the context dimension of the cube view.

    That is not what I'm needing.  The problem dimension has two hierarchies.  The alternate is an attribute hierarchy of the default hierarchy.  I want to select some parent elements in the attribute hierarchy and return the children from the base hierarchy.

    The multi-selector is the alternate hierarchy parents.  What I want to do is select two parents in the selector (alternate hierarchy parents) and drive the  default hierarchy to return the children (and only the children) of the selected parents of the alternate.

    I am able to do this using an extra cube.  The user flags a cell for the desired parents in the cube view of the attribute hierarchy and then an MDX set uses that cube to filter and return the children of those parents in the default hierarchy.  If I could grab that subset that is returned by the multi-selector list or in the context dimension somehow, I would not need the extra cube.  I hope this makes sense for what I am trying to do.

    Ty



    ------------------------------
    Ty Cardin
    ------------------------------

    Original Message


  • 5.  RE: Multiselector lists

    Posted Tue January 28, 2025 04:39 PM

    Stuart,

    Played around some more with the selector lists.  Yes, it would be great to have a children of set option for Action on set change.



    ------------------------------
    Ty Cardin
    ------------------------------

    Original Message


  • 6.  RE: Multiselector lists

    Posted Tue January 28, 2025 09:18 PM

    Additional 'Advanced synchronization' options would be helpful in many cases.  Your use case is a bit more complex as the synchronization feature in PAW books only synchronizes the same hierarchy between different widgets.  In your case you want to synchronize different hierarchies (where you have defined some relationship between the members in each).  This might require a more open ended approach like Ryan is suggesting.  We could consider a custom 'Advanced Synchronization' option where you can parameterize the MDX statements for each widget.

    Make sure you look carefully at the release notes for the upcoming PAW 2.0101 or 2.1.8 release.  

    In the mean time, I suspect that creating a lookup cube in TM1 to store the relationship between members in the each hierarchy is the only good solution.   



    ------------------------------
    Stuart King
    Product Manager
    IBM Planning Analytics
    ------------------------------

    Original Message


  • 7.  RE: Multiselector lists

    Posted Wed January 29, 2025 07:03 AM

    Hi,

    I really like @Ryan Clapp's idea and have been hoping for something like this for several years. If I remember correctly, it was even on the public roadmap at one point. I actually found the original roadmap text:

    Q2 2022: "Synchronize Parameters in MDX Statements | Support complex synchronizations by allowing parameterized MDX statements to drive synchronization between widgets."

    A custom 'Advanced Synchronization' option that allows parameterized MDX statements for each widget would be a great addition!



    ------------------------------
    Mario Hasler
    ------------------------------

    Original Message


Related Content