TM1 Forum

Hi There

Some reporting in the company I work for uses public subset names - and this works as long as you are either Admin or Data admin - obviously this is not a viable solution for every user. Other users not of those security groups get #N/A when they use the public subset names in reports.

Anyone come up against this before and is there a solution rather than adding additional hierarchies into the dimension structure?

Tim

Hi Tim,

This sounds as though the problem is with element security rather than the subset. How are your reports built exactly?

Cheers,
Alex

edit: Tim, not Ian. I haven't even started on the wine yet.

timrrmuphy wrote:Some reporting in the company I work for uses public subset names - and this works as long as you are either Admin or Data admin - obviously this is not a viable solution for every user. Other users not of those security groups get #N/A when they use the public subset names in reports.

Taking a bit of a guess at what you mean... you have some reports where the DBRW formula references the name of a subset rather than an element which has the effect of giving you the sum of the elements in the subset as if it was a consolidation point... If I'm right then I believe this is still an 'undocumented' feature that is subject to change or removal by IBM at any time. I agree with Alex that this sounds like a security issue - although security isn't set on a subset it may be that a public subset with elements for which a user has no security privelege may be upsetting the 'subset as element' feature.

timrrmuphy wrote:is there a solution rather than adding additional hierarchies into the dimension structure?

I'd recommend that additional hierarchies ought to be your default reporting standard rather than be seen as an alternative, or work-around. Although everyone recognises that being able to reference the subset is extremely useful it is also hard to troubleshoot and is more than likely unsupported.

Yes the assumption is correct - the report uses a subset name and if you are either DataAdmin or Admin then the report works with Cognos Express.

I have checked the securities against evrything on the element list for the Subset and the users have write access to all elements.

I as you say it is an little known feature then we will have to use dimension hierarchy instead. Thanks though...