Dimension element Security

[appleglaze28]

I'd like to ask, I just noticed something with what I'm doing...I have this process that creates a dimension along with hierarchy base on a CSV extracted file from TM1. I was just wondering how come when I create new dimension elements for that specific dimension the security of the groups are NONE instead of the typical WRITE setting that I noticed dimensions adopt for new elements in the dimension.

[Alan Kirk]

I'd like to ask, I just noticed something with what I'm doing...I have this process that creates a dimension along with hierarchy base on a CSV extracted file from TM1. I was just wondering how come when I create new dimension elements for that specific dimension the security of the groups are NONE instead of the typical WRITE setting that I noticed dimensions adopt for new elements in the dimension.

It depends on whether you really have security set on the dimension elements at all; in other words, whether there's a }ElementSecurity_ cube for that dimension. If there is then by default any new elements will have a security value of "None" until you explicitly change that (or have rules which will do that for you).

If there isn't, and you look at the Elements Security Assignments... dialog you'll see the "security" as "Write" for existing and new elements... but this slightly misleading in that the elements are "write" enabled simply because there has been no security at all explicitly applied to them.

[appleglaze28]

Well I wrote a TI to once that element has been added to the dimension to write in the {ElementSecurity for that dimension in all groups as WRITE...however, I'm getting this error that Cell Type is consolidated however, what I'ma added to the dimension is on element leve so why is it that I get that error, although when I check the cube, the process runs fine.

Or is this error more related to the ADMIN, DataAdmin & SecurityAdmin groups?

[Alan Kirk]

Well I wrote a TI to once that element has been added to the dimension to write in the {ElementSecurity for that dimension in all groups as WRITE...however, I'm getting this error that Cell Type is consolidated however, what I'ma added to the dimension is on element leve so why is it that I get that error, although when I check the cube, the process runs fine.

Or is this error more related to the ADMIN, DataAdmin & SecurityAdmin groups?

Might be an idea to post the code, because that error doesn't make sense. All of the Element Security elements are effectively strings which means that TM1 doesn't care whether the element that it's writing to is a consolidation or not.

[appleglaze28]

Code: Select all

#*****************INPUT DEFAULT "WRITE" SECUTIY*****************************
i = DIMSIZ('}Groups');
while(i>1);
  group = DIMNM('}Groups', i);
              CellPutS('WRITE','}ElementSecurity_base_worksheet_so_number',v3,group);
              CellPutS('WRITE','}ElementSecurity_base_worksheet_so_number',v1,group);
              CellPutS('WRITE','}ElementSecurity_base_worksheet_so_number','TOTAL CLIENTS',group);
  i = i - 1;
end;

I put this code on the uppermost part of the Data Tab

[asutcliffe]

I have a similar issue. I have a number of TI processes that add new elements to dimensions. I want members of a power user group to run these processes and to gain WRITE access to the new elements. As it stands the process adds the element but they get NONE access to them. I have tried putting the following in the epilog of my process:

Code: Select all

ElementSecurityPut('Write', 'DataVersion', NewDataVersion, 'POWER');

It fails with 'No Security Access for "ElementSecurityPut"'. I thought that this might work given that I'd given the POWER group WRITE access to cube }ElementSecurity_DataVersion and WRITE to }Groups dimension. Presumably this fails because it doesn't have WRITE access to the new element I'm adding? I get the feeling I am going about this wrong...

* Would adding a rule to the }ElementSecurity_DataVersion cube be a better approach?
* Can I remove element security altogether for this dimension so that new elements can be accessed by default by simply deleting cube ElementSecurity_DataVersion?

Cheers,
Alex

[asutcliffe]

I have resolved this by using a rule. but had to set security access on the process to refreshsecurity anyway (as per http://forums.olapforums.com/viewtopic. ... 677#p11677). If I'd done this in the first place presumably the call to ElementSecurityPut would have worked.