Good day.
I'm trying to burst to a distribution list. I've added a burst table to the database with two columns: BurstID and BurstValue where BurstID contains all references to the groups in the distribution list, and BurstValue is the CAMIDs of these groups.
When I'm creating my report, I have a xtab and I've placed this xtab within a list, then sectioned the list on the BurstID. This report fails likely because there is no security defined in my cube so that BurstID value1 can only see x-data, BurstID value2 can only see y-data, etc.
The question I have is, is the only way around this to define security within the cube? Thoughts?
How are you relating the burst table to the report query?
I have done this without adding security to a cube, so yes, it can be done. I am not sure I understand the make-up of your burst table.
Quote from: rockytopmark on 28 Apr 2008 01:13:49 PM
How are you relating the burst table to the report query?
I have done this without adding security to a cube, so yes, it can be done. I am not sure I understand the make-up of your burst table.
This is where I'm stuck. My burst table literally has two columns with the BurstID (Region) and BurstValue (CAMID). So each region has a specific CAMID, but I'm trying to define a relationship between a cube and this burst table within Report Studio so that the relevant data is split on each region.
Does your cube also have the RegionID as one of the Level's category codes or labels? This would be necessary. Do not attempt to join on the MUN, this will not do you any favors. You need to reference the Level's attribute that matches the Relational RegionID value in the burst table.