Element Security without Mass number of User Groups

Post Reply
redwin42
Posts: 3
Joined: Thu Nov 15, 2012 7:52 pm
OLAP Product: TM1
Version: 9.5.1
Excel Version: 2007

Element Security without Mass number of User Groups

Post by redwin42 »

I'm pretty sure this has been discussed before, so I apoligize if it is a duplicate. I have done some searches for this but have come up empty.

I have about 200 sales reps that are on a commission plan. I have created a few cubes to manage the commissions. Using these cubes I have pushed out a goalsheet with the goals and payouts by quarter. Upto this point I have had to create one security group for each rep, so that each rep only has access to their information. The security group is then matched to the sales Rep ID in the Sales Rep dimension.

Is there a better way to assign security for the reps? Visually I see a table that has their login ID and their Sales Rep ID. TM1 then only displays the Rep ID that is associated with the login in this table. I read a little on picklists, but don't know if that is what I want fully.

Any help would be greatly appreciated.

Thank you!
User avatar
jim wood
Site Admin
Posts: 3961
Joined: Wed May 14, 2008 1:51 pm
OLAP Product: TM1
Version: PA 2.0.7
Excel Version: Office 365
Location: 37 East 18th Street New York
Contact:

Re: Element Security without Mass number of User Groups

Post by jim wood »

Something related to this has been discussed before but not identical. If you do a search for custom workflow you'll find that security is a fundamental part of doing that.

As for your question specifically, I think (keeping in mind it's getting towards the end of the day and all 2 of brain cells are in need of charge) that you're pretty much stuck with your one user one group approach.

I guess the question then becomes how you would apply that. It is possible to do so via rules on the security cubes as you only have 200 reps. The thing with this approach that you need to keep in mind is that you'll need to refresh security every time you update the reps or data. As you only have 200 of them this shouldn't take that long. Another way might be to have a database table that you can use to map the uses to groups and then groups to elements. Again you'll have to keep security refreshes in mind.

Do they really need access. Couldn't you just produce a report per rep?

I hope that helps,

Jim.
Struggling through the quagmire of life to reach the other side of who knows where.
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
PlanningDev
Community Contributor
Posts: 349
Joined: Tue Aug 17, 2010 6:31 am
OLAP Product: Planning Analytics
Version: 2.0.5
Excel Version: 2016

Re: Element Security without Mass number of User Groups

Post by PlanningDev »

If you are careful about how you setup the element names and group names you should easily be able to automate this through a TI. All you have to do is loop the sales person dimension and create groups and assign users with the same name to the group then do a security refresh at the end
redwin42
Posts: 3
Joined: Thu Nov 15, 2012 7:52 pm
OLAP Product: TM1
Version: 9.5.1
Excel Version: 2007

Re: Element Security without Mass number of User Groups

Post by redwin42 »

Thank you both for your help with this. I greatly appreciate it.
wiliamjack703
Posts: 1
Joined: Wed Aug 28, 2013 6:24 am
OLAP Product: Browser
Version: 3.0
Excel Version: 2013

Re: Element Security without Mass number of User Groups

Post by wiliamjack703 »

jim wood wrote:Something related to this has been discussed before but not identical. If you do a search for custom workflow you'll find that security is a fundamental part of doing that. I checked this and found a solution.

As for your question specifically, I think (keeping in mind it's getting towards the end of the day and all 2 of brain cells are in need of charge) that you're pretty much stuck with your one user one group approach.

I guess the question then becomes how you would apply that. It is possible to do so via rules on the security cubes as you only have 200 reps. The thing with this approach that you need to keep in mind is that you'll need to refresh security every time you update the reps or data. As you only have 200 of them this shouldn't take that long. Another way might be to have a database table that you can use to map the uses to groups and then groups to elements. Again you'll have to keep security refreshes in mind.

Do they really need access. Couldn't you just produce a report per rep?

I hope that helps,

Jim.
I stuck with your instruction you write. Can you make it a bit more clear your instruction? Cause that seems very difficult.
Post Reply