Planning Analytics

 View Only
  • 1.  dynamic subset issue

    Posted Mon March 20, 2023 09:22 AM

    Has anyone else had the MDX in their subsets disappear randomly?  Periodically, MDX won't be in a subset that we use primarily as a locations selector.  That will turn our subset from dynamic to static which will list the incorrect elements for users.  It's an easy enough fix to update the MDX of the subset.  It's just annoying and not a very good look to our end users (getting something so basic wrong).   

    Is this a known bug?



    ------------------------------
    Matthew Newman
    ------------------------------


  • 2.  RE: dynamic subset issue

    IBM Champion
    Posted Mon March 20, 2023 10:53 AM

    Do you mean that an MDX subset is becoming a static subset?

    Or a view/subnm etc which was saved with an MDX subset is instead showing a different set/list of elements?

    If its the latter; opening a set editor and expanding/collapsing elements etc means the user is now working with their own selections instead of the original subset. In perspectives it used to come up with a warning as they did this.

    If your subset is actually becoming static and "losing" the MDX; it is not a known bug that I am aware of. I would imagine that an action is causing it to happen; this could be that a user is clicking the save button and overwriting the subset - or potentially there is a TI process running which alters the subset.

    For "public" subsets only users with "Admin" access (to the model OR just the relevant dimension) will be able to save it. So I would recommend checking if the user access that you have is strict enough. You should also be able to look at the "date modified" on the subset to find when it was last altered (e.g. changed from dynamic to static) and check the logs to see if there were any processes running at that time.



    ------------------------------
    Declan Rodger
    Technical Director
    Spitfire Analytics
    ------------------------------



  • 3.  RE: dynamic subset issue

    Posted Mon March 20, 2023 01:02 PM

    The subset is actually becoming static and "losing" the MDX.  In the set editor, it is there one day and gone the next.  I'll check on access.  Thanks.



    ------------------------------
    Matthew Newman
    ------------------------------



  • 4.  RE: dynamic subset issue

    Posted Tue March 21, 2023 03:12 AM
    Edited by Laurent Henssien Tue March 21, 2023 03:12 AM

    Hello Matthew, 

    I've been working with these for years and never had this issue (I've had other issues but that's another discussion 😅)

    As Declan says usually when this happens a user presses the save button after changing the selection. I have had the event happening from time to time with certain functional administrators with extended rights to the application. When this happens too often I just set up a process to rebuild all standard MDX subsets overnight...

    Cheers, 


    ------------------------------
    Laurent Henssien
    C L A R I T Y
    https://www.clarity.consulting
    ------------------------------



  • 5.  RE: dynamic subset issue

    Posted Tue March 21, 2023 08:39 AM

    I've noticed that when I check some subsets to verify the MDX, it has changed to something like this.   TM1SubsetToSet([Market].[Market] , "subset3" , "public").  I haven't been able to verify if it is static or still dynamic since I no longer know what the original MDX was.

     

    Thank you,

     

    Mitch

     

     

    Mitch Petty | TM1/Planning Analytics Developer

    Huntsman Advanced Materials Americas |10003 Woodloch Forest Drive |The Woodlands, TX | USA

    ( 281-719-4209| * mitch_petty@huntsman.com

     

     






  • 6.  RE: dynamic subset issue

    IBM Champion
    Posted Tue March 21, 2023 12:10 PM

    HI Mitch,

    Typically when you open the set editor and the MDX shows TM1SubsetToSet(...) it means that you have a static set.

    The elements are obviously alongside but would be good to be able to evaluate the MDX in the MDX window to return the elements for when changes are needed rather than selecting, copying, pasting, saving as to copy the set name, cancelling, committing then saving for real and pasting the set name from the clipboard.

    I know Svetlana is aware of the above as this has been discussed previously.



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



  • 7.  RE: dynamic subset issue

    Posted Tue March 21, 2023 01:59 PM

    Hi all,

    TM1SubsetToSet is expected in the case of static sets as an optimization to avoid killing the browser.

    However not the dynamic sets. It's been cases where the users would accidently convert from the dynamic to a static sets to be surprized with this optmization taken place.



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



  • 8.  RE: dynamic subset issue

    Posted Wed March 22, 2023 01:27 PM

    I saw this for the first time the other day; no matter what I did to the selection and subsequent save, it kept reverting back to static with the SubsetToSet call. 

    Found it happened with a handful of our sets; the only commonality I could find was that the subsets exhibiting the behavior were created in the legacy tools (Architect/Perspectives). We created a new set and it worked fine. 



    ------------------------------
    Matthew Berson
    ------------------------------



  • 9.  RE: dynamic subset issue

    Posted Thu March 23, 2023 05:44 AM

    Let me start by answering the first question "Is this a known bug?", as far as I'm aware it is not. If anybody has a reproducible case, one that would demonstrate this unintended side effect of converting a dynamic subset into a static one (read: remove the MDX expression from the subset and substitute the static list of elements with a snapshot of the set of represented elements at that point in time) I'd love to take a look at it (and fix it for you).

    That said, given the comments pertaining to TM1SubsetToSet, allow me add that TM1SubsetToSet is the preferred (and in the next major version of TM1 - v12 - the only) way to refer to a 'traditional' TM1 [sub]set of elements from within an MDX set expression (either as part of an MDX query, a MDX set definition or a dynamic subset's MDX expression).  Use of this function by itself does not do anything with the subset being referenced. When the MDX including such TM1SubsetToSet is being executed the subset's list of elements is 'converted' to members (this typically opaque unless an element has multiple parents in which case one of the members representing the relationship with one of its parents has to be chosen to represent such element) which then subsequently are being used to build the overall result of that MDX. If the subset being referenced is itself a dynamic subset again (read: has an MDX expression) then that MDX expression is being executed to come up with the list of elements that subset represents at that point in time.

    Hope that helps,



    ------------------------------
    Hubert Heijkers
    STSM, Program Director TM1 Functional Database Technology and OData Evangelist
    ------------------------------