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
------------------------------
Original Message:
Sent: Wed March 22, 2023 01:26 PM
From: Matthew Berson
Subject: dynamic subset issue
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
Original Message:
Sent: Sun March 19, 2023 08:32 PM
From: Matthew Newman
Subject: dynamic subset issue
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
------------------------------