Bursting and Security Groups

[okh310]

I have created a report that should burst by contract.  I have my users set up in AD and have created groups to handle security.  As a test, I am specifying the CAMID of one contract group as the burst recipient key (hardcoding that camid in the report).  What I expect to happen when I run the report, the user in that group should ONLY get their contract portion of the report.  Instead, they are getting the entire report.                                     
                                                                       
When I log in as the user and run the report (unbursted version) they are only able to see their contract.                                   
                                                                       
My question is, SHOULD bursting taking into account security when using CAMID??                                                                 
                                 

[MFGF]

I have created a report that should burst by contract.  I have my users set up in AD and have created groups to handle security.  As a test, I am specifying the CAMID of one contract group as the burst recipient key (hardcoding that camid in the report).  What I expect to happen when I run the report, the user in that group should ONLY get their contract portion of the report.  Instead, they are getting the entire report.                                     
                                                                       
When I log in as the user and run the report (unbursted version) they are only able to see their contract.                                   
                                                                       
My question is, SHOULD bursting taking into account security when using CAMID??                                                                 
                               

Hi,

The simple answer is it depends. The burst specifications you define should specify two things:
1. How the output is divided up - this is driven by the grouping you specify in the burst properties.
2. Where each output is sent - this is driven by the burst key you specify in the burst properties.

Obviously, a burst key needs to be associated somehow with the value(s) you group on. If all groups have the same burst key, then you are effectively sending the entire output to one destination. I think the part you are missing here is that there should be a link between contract and CAMID - often this is defined by creating a burst table with Contact ID and CAMID in it, and adding this burst table to your model so you can reference it in your report.

Cheers!

MF.

[okh310]

Hi MFGF -

Thank you for the response.  My security is set up in TM1.  I have assigned certain people to groups and then assigned the group to specific Contracts.  So for my "test", if I just hardcode the CAMID from a group, I would expect all contracts that do NOT belong to the group to just get ignored - no emails/burst.  I would expect the one group, would get just the ONE portion of the report that belongs to that contract/group assignment. 

So when using CAMID with bursting does it ignore the security that has been set up in TM1?

[okh310]

I guess I should explain my thinking behind this idea.  So my thinking is that I could create a distribution list and add all the contract groups in there.  Then I could just reference the CAMID of the distribution group and the TM1 security would be smart enough to know which group gets what portion of the report.

[MFGF]

Hi MFGF -

Thank you for the response.  My security is set up in TM1.  I have assigned certain people to groups and then assigned the group to specific Contracts.  So for my "test", if I just hardcode the CAMID from a group, I would expect all contracts that do NOT belong to the group to just get ignored - no emails/burst.  I would expect the one group, would get just the ONE portion of the report that belongs to that contract/group assignment. 

So when using CAMID with bursting does it ignore the security that has been set up in TM1?

Hi,

What you say you're expecting here isn't the way it works, sadly. If you hard-code a CAMID, then it's going to apply to all rows in the report. It's the group-by item in bursting that drives what data is in which section, and the burst key is used to define where each section is delivered to. The burst key doesn't act as any sort of filter - it's just a location to send the outputs to. It isn't looking at the security set up in TM1 - bursting is controlled by the burst specifications you have defined within the report.

I guess I should explain my thinking behind this idea.  So my thinking is that I could create a distribution list and add all the contract groups in there.  Then I could just reference the CAMID of the distribution group and the TM1 security would be smart enough to know which group gets what portion of the report.

No - not unless you have defined a link between a distribution group and a TM1 group in your report or in your data. You need to figure out how to resolve the group-by item in the burst specifications with the burst key values in the burst specifications.

MF.