TM1 Forum

Guys,

I'm pretty certain I know the answer to these questions but here goes....

1) Can you set security for subsets?
2) Can you use subsets (rather than consolidations) to control access to elements within element security via rules? (I know you can do it easily using TI)

Thanks,

Jim.

jim wood wrote: I'm pretty certain I know the answer to these questions but here goes....

1) Can you set security for subsets?

No, only elements within them. If you want to draw a longer bow than even Robin Hood could manage, you could have a TI assign security to those elements based on membership or not of the subset (which leads us to our next point below), but that doesn't affect whether the user can see the subset. For that, all you have is either public or private.

jim wood wrote:2) Can you use subsets (rather than consolidations) to control access to elements within element security via rules? (I know you can do it easily using TI)

No. In fact off the top of my head I can't think of any officially supported, non-Easter egg rule functions that you can use with subsets, primarily because it would make the rule calculations rather unpredictable and dependent on the contents of a subset at any given time which would hardly enhance TM1's reputation for reliability. It's worth noting that there is no rule equivalent of (for instance) SubNm. It could be argued (not persuasively, but it could be argued) that this is also the reason that SubsetGetElementName has such a bizarre name compared to SubNm; to emphasise the fact that "this is a TI function only and there ain't no rule equivalent.