Controlling views by approval hierarchy node
Posted: Sat Jun 05, 2010 7:47 pm
Hi Everyone,
Does anyone know if it is possible to control which views are used at node level in an approval hierarchy in TM1 Contributor. For instance, view 1 and view 2 are based off of the same cube. View 1 has accounts specific for node 1, and view 2 contains accounts specific for node 2. What I want to do is ensure that a user only sees view 2 when they open node 2 in TM1 contributor. In Cognos Planning, this would be similar to access tables. I am not sure how it is done in TM1 contributor. Maybe i am looking at this too much from a cognos planning angle rather than a tm1 angle. Alternatively, I can control what subsets are used by node by just entering the application and specifying which subset to use for each node. This would work, however, if I update the application, the subset previously specified is reset. So I would have to re-specify it everytime the application is updated.
Any advice would be greatly appreciated. Thank you!
Does anyone know if it is possible to control which views are used at node level in an approval hierarchy in TM1 Contributor. For instance, view 1 and view 2 are based off of the same cube. View 1 has accounts specific for node 1, and view 2 contains accounts specific for node 2. What I want to do is ensure that a user only sees view 2 when they open node 2 in TM1 contributor. In Cognos Planning, this would be similar to access tables. I am not sure how it is done in TM1 contributor. Maybe i am looking at this too much from a cognos planning angle rather than a tm1 angle. Alternatively, I can control what subsets are used by node by just entering the application and specifying which subset to use for each node. This would work, however, if I update the application, the subset previously specified is reset. So I would have to re-specify it everytime the application is updated.
Any advice would be greatly appreciated. Thank you!