Dynamic Subsets turning static

[Aerouge]

Hy guys,

another strange behaviour... I defined a dynamic Subset using MDX. It gets created and shows the filter icon.

The subset "apparently" turns static after a few seconds though and the expression used to define it is lost as well if I open it in the Subseteditor.

Looking into the SUB-File the expression is still there though. Is this a display bug? Why is the expression lost, if I open the subset again?

If anyone has encountered this behaviour or can share some insights I´d greatly appreciate it.

Thanks in advance!

[Alan Kirk]

another strange behaviour... I defined a dynamic Subset using MDX. It gets created and shows the filter icon.

The subset "apparently" turns static after a few seconds though and the expression used to define it is lost as well if I open it in the Subseteditor.

Looking into the SUB-File the expression is still there though. Is this a display bug? Why is the expression lost, if I open the subset again?

If anyone has encountered this behaviour or can share some insights I´d greatly appreciate it.

Thanks in advance!

In what environment?

If you're talking about the subset editor in classic Perspectives you would need to manually open the Expression Window from the View menu to see the MDX; it doesn't open automatically when you open the subset in Subset Editor.

[declanr]

This sounds like a bug that caused me to question my sanity last week: https://ibm.com/support/pages/apar/PH31597

IBM have stated its planned to be resolved in PA 2.0.9.6 LC and PA 2.0.9.1 IF 7

The incident and support team suggest that there are many potential causes of this which have not yet been narrowed down (for me), in my case one MDX expression got removed if any metadata changes were made to the dimension. My temporary workaround is to call a second process via RunProcess that adds the MDX expression back to the subset after the first process has completed its metadata commitments.

But the name of the APAR suggests it may not just be metadata changes that cause it, so if you are experiencing one of the other causes then it may be harder to get a workaround in place.

[Aerouge]

In what environment?

If you're talking about the subset editor in classic Perspectives you would need to manually open the Expression Window from the View menu to see the MDX; it doesn't open automatically when you open the subset in Subset Editor.

Hy Alan, nope I use the Subset-Editor in TM1-Architect exclusively.

[Aerouge]

This sounds like a bug that caused me to question my sanity last week: https://ibm.com/support/pages/apar/PH31597

IBM have stated its planned to be resolved in PA 2.0.9.6 LC and PA 2.0.9.1 IF 7

The incident and support team suggest that there are many potential causes of this which have not yet been narrowed down (for me), in my case one MDX expression got removed if any metadata changes were made to the dimension. My temporary workaround is to call a second process via RunProcess that adds the MDX expression back to the subset after the first process has completed its metadata commitments.

But the name of the APAR suggests it may not just be metadata changes that cause it, so if you are experiencing one of the other causes then it may be harder to get a workaround in place.

Thanks for the link and nope it´s not changes to the Dimension. This happens seconds after me saving the dynimc subset in TM1-Architect. Especially since only some subsets turn static while others remain dynamic this has me utterly bamboozeld. And I totally get why this has anybody question ones sanity.

At least your post confirms my suspicion that it´s not me beeing unable to create a dynamic subset (after doing this sucessfully for 15 years) but is rather a topic for the IBM-Support. SO thanks for your post

[Alan Kirk]

In what environment?

If you're talking about the subset editor in classic Perspectives you would need to manually open the Expression Window from the View menu to see the MDX; it doesn't open automatically when you open the subset in Subset Editor.

Hy Alan, nope I use the Subset-Editor in TM1-Architect exclusively.

You ARE aware that Perspectives, Architect and Client are all exactly the same user interface, with Architect just lacking Excel integration, yes?

It may indeed be that you are encountering the problem that Declan mentioned, depending on which SPECIFIC version of the software that you're on (which isn't in your profile and hasn't been mentioned in this thread; 2.0.what?), but otherwise it still does raise the question of whether you have looked in the Expression window or not.

This is because of what you said here:

Looking into the SUB-File the expression is still there though.

IF that really is the case, then it would sound almost as if the server has forgotten how to read its .sub files which should invalidate any and all MDX expressions.

Something there does not gel to me.