Cube Security Assignment - No Equivalent for the TM1 Security Assignments dialog ( }CubeSecurity cube)
Is your feature request related to a problem? Please describe.
It's a problem that comes up fairly rarely, but without Perspectives it tends to be fiddly.
- You create a new cube.
- You right click on the Cubes list and select Security Assignments...
- You scroll, and scroll, up and down, left and right hoping that the form keeps redreawing itself until you find the intersection of the new cube with the security access group that you want and click a radio button to set the security level, and click on the [OK] button to lock it in.
- Can't you do this with a quick TI? Sure, except that IBM never provided a function to do that.
- Can't you just punch the access level into the }CubeSecurity cube?
- Sure, and in fact it's the only way that you can do it with Arc. The problem is that for all its ugliness, the Perspectives dialog performs one useful function; it ensures that security is ALSO assigned to the cube's DIMENSIONS. If you punch in the access directly to }CubeSecurity you can end up with a cube that the users have access to... but they have no access to the dimensions.
Proof: This is what happens when I set access using the dialog in the Prod environment:
"","20221130233242","20221130233242","AdminAK","S","","READ","}CubeSecurity","PAY_Employee_Master_Data","MOD_PAY",""
"","20221130233242","20221130233242","AdminAK","S","","READ","}DimensionSecurity","PAY_Master_Data_Period","MOD_PAY",""
"","20221130233242","20221130233242","AdminAK","S","","READ","}DimensionSecurity","PAY_EmpID_All","MOD_PAY",""
"","20221130233242","20221130233242","AdminAK","S","","READ","}CubeSecurity","}ElementAttributes_PAY_EmpID_All","MOD_PAY",""
"","20221130233242","20221130233242","AdminAK","S","","READ","}DimensionSecurity","}ElementAttributes_PAY_EmpID_All","MOD_PAY",""
"","20221130233242","20221130233242","AdminAK","S","","READ","}DimensionSecurity","PAY_Employee_Master_Data_Measure","MOD_PAY",""
"","20221130233242","20221130233242","AdminAK","S","","READ","}CubeSecurity","}ElementAttributes_PAY_Employee_Master_Data_Measure","MOD_PAY",""
"","20221130233242","20221130233242","AdminAK","S","","READ","}DimensionSecurity","}ElementAttributes_PAY_Employee_Master_Data_Measure","MOD_PAY",""
The log file shows that }DimensionSecurity is automagically updated as well.
However in the Dev environment (which was an exact copy of the Prod environment taken earlier in the day), an input straight to the cube yielded only this line:
"10e63","20221130233858","20221130233858","AdminAK","S","","READ","}CubeSecurity","PAY_Employee_Master_Data","MOD_PAY",""
#"10e63","20221130233859","Change set 10e63 complete : 1"
Describe the solution you'd like In an ideal world it would be nice to have a tab where we could set security on a new cube, and cause the security assignments to be made for the dimensions as well just as Perspectives does.
(In reality, it's a releatively low priority "nice to have"; it's not like we create multiple cubes a day in most cases.)
Describe alternatives you've considered
For now, I just use Perspectives.
If Perspectives were to be no longer available, I'd just have to set the access for the dimensions and attributes of the dimensions manually