[Solved] parent level for bursted currentmember

[charon]

Hi,

similar to my last challenge.

Is there ANY WAY to get a parent level for burst member in a bursted report?
Example: Busrting Article ID, is there a way to get the revenue for all Articles in the parent level, e.g. Producttype Tents?
I have to deliver the ID with a master-detail relationsship, and the result is, i have only the measures for the 1 article id the report is for (bursted Article id).

I would appreciate any ideas pretty much...ty all and cheerz :P

=> Apparently, there is no direct/ easy way. Bursting is a relational concept, therefore working with dimensional data structures wont workt that well.
One workaround is to model the queries/ filters relational. Then get all data for the parent level. In the third step join the queries and use the data items with the parent level data.

Issue might be the performance, depending on the complexity of the modell.
cheerz :P

[Lynn]

I have just recently implemented a bursted report with a cube data source. In my case the content is burst to a network drive.

It allows selection for a level in the location dimension (division, region, etc) and creates a separate file per each descendant. For example, selecting "Region" would yield one report for Eastern Region, one for Central and one for Western. The prompt "use" value is an expression to return the relevant members:

Code Select Expand

filter( descendants ( members ( [MyCube].[All Locations].[All Locations].[Continent] ) , 1 ), tuple ( [SPECIAL ITEM CATEGORY], [Item Count] ) >= 1 )

The report contains multiple layout containers (crosstabs and charts) that are connected to a main burst query via master detail relationships. The burst query and each report query contains a data item with a prompt macro expression that is the basis for the master detail relationship:

Code Select Expand

#prompt ( 'pLocationGroup', 'token' )#

Also, some of the layouts on the page show children of whatever level is selected. So if you chose region then one particular crosstab shows the children of the region. For example, the Eastern Region report would show sub-regions Northeast and Southeast. This is achieved by using a data item with this expression:

Code Select Expand

descendants ( #prompt ( 'pLocationGroup', 'token' )#, 1 )

It seems to me that using a similar approach with the ancestor instead of descendants function might be something worth investigating for your situation

P.S. I figured out how to do this by reading PaulM's posts on the subject of prompt macros and dimensional reporting. Thank you Paul!!!  8)

[charon]

Awesome, gone try this during the weekend. Looks promising..ty Lynn  :D (and Paul ;)

[charon]

hm, i was not able bring it to work for now, but i gonne try it during the week. still, ty for the idea :)

[CognosPaul]

Ears were burning  ;D

Bursting is simply another manifestation of master/detail relationships. And those are certainly not solely relational concepts.

So if I understand correctly, you have a query which is returning n products. Part of the data container needs to show the revenue for the parent (possibly to get a revenue % for the product). In this scenario, you should have the following:

Master/detail on product --> product level. In order to get the parent, you would need the following: parent(currentMember([Cube].[Product Dim].[Product Hierarchy]))

Alternatively, you could try the following:
Create a data item Product with: #prompt('Product','mun','DefaultMUN')#
Product Type would be: parent([Product])
Point the master detail to pass the value to the Product parameter, instead of trying to match up against a level.