created a calculated member CREATE MEMBER CURRENTCUBE.[Team].[Project].&[4446].Utopia AS Aggregate({[Team].[Project].&[4474],[Team].[Project].&[4455], [Team].[Project].&[4448], [Team].[Project].&[4475],[Team].[Project].&[4520]}) Now created some security roles, but when I attempt to slice through the cube using the security role, the cells show #VALUE! Msg: '(The level &[4474] object was not found, in the cube when the string [Team].[Project].&[4474] was parsed)'. The 'artificial' members need to be created, so they have to be specified in the cube. Has anyone encountered this problem between calculated members/security roles. How can I exclude the calculated member from this role.
This blog entry should give you some ideas on how to handle it: http://cwebbbi.spaces.live.com/blog/cns!7B84B0F2C239489A!1563.entry >> Dimension Security Tips, Tricks and Problems .. Then there's the problem of calculations and security. If you read Mosha's blog entry here on the subject of cube initialisation you'll see that the MDX Script is executed after dimension security is applied - so if you reference a member in your MDX Script that has been secured, then it could result in an error. .. >> - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com ***
