Dynamic subset is no longer working

[smile_netz]

Hi All,

I'm very new in TM1 Cognos and I'm hoping you could help me.
We have encountered this issue just recently where a dynamic subset is no longer working in one of our environments. Our dev environment has this particular subset still working. I'm thinking to just copy it over to the other environment.
Can someone please teach me which files I need to copy or how I could rebuild the dynamic subset?

Thank you.

[Steve Rowe]

You ought to try and understand why it is not working rather than just copying the file.

The subset had a piece of MDX assoicated with it with you can see by selecting view expression in the subset editor.

Assuming the piece of MDX has not changed then it's likely that the reason it is not working is that whatever the MDX is referencing has changed rather than a problem with the subset itself.

If you post the MDX then someone can point in the right direction for that.

Cheers

[qml]

Can you tell us what you mean when saying the subset is "not working"?

Sometimes it happens that a dynamic subset (with an MDX formula attached) gets overwritten by a static subset and stops being dynamic (but it still works in the sense that it returns a list of elements). This you can easily tell by the different icon showing next to the subset's name.

Another reason that a dynamic subset might stop working (and start throwing an error) is described in Steve's post.

[smile_netz]

In the expression Window on our UAT environment (this is the environment where this subset is no longer working), this is what it says:
{ HIERARCHIZE( {TM1DRILLDOWNMEMBER( {TM1SubsetBasis()}, ALL, RECURSIVE )} ) }

In our DEV environment,
{TM1DRILLDOWNMEMBER( {TM1SubsetBasis()}, ALL, RECURSIVE )}

*** I am trying to edit the subset to look like the DEV but there are just no values coming out. The "not working" in my context means that all the elements are gone so there are no values shown in the cube where this dimension is being used.

Please advise.

Thanks.

[smile_netz]

Thanks all for your reply.
I was able to recreate the subset. Our Finance team managed to create different accounts on different nodes that cause all the dynamic subsets not to list any elements.

[rmackenzie]

Obviously you can see the difference between the MDX expression between the environments. The extra HIERARCHIZE function in your UAT environment will rejig the subset to organise the members of specified set into their hierarchical (tree-like) order.

That wouldn't account for your having an empty subset - what would is that the {TM1SubsetBasis()} part of both expressions is evaluating differently in DEV and UAT. The TM1SubsetBasis function means the dynamic expression should use whatever elements were in the subset when the expression was first recorded. This subset may well be different between DEV and UAT. Going forward, you will always have unpredictable results when using this function - i.e. it's only good for the initial development.

As well as aligning the expressions to either both use HIERARCHIZE or both not use it, you should replace the TM1SubsetBasis function with a hard-coded reference to the element that you are drilling down on. For example, if this is you cost centre dimension you should use something like this:

Code: Select all

{TM1DRILLDOWNMEMBER( {[Cost Centre].[All Cost Centres]}, ALL, RECURSIVE )}

Or e.g. for your general ledger account dimension:

Code: Select all

{TM1DRILLDOWNMEMBER( {[GL Account].[All GL Accounts]}, ALL, RECURSIVE )}