Sets and Hierarchies for bursting

ReportWORQ
1

Hi,

I need to build a bunch of sets to drive bursting of reports. I’d like them not to clutter up the PAW UI for the PAW users though.

I could create a hierarchy specifically to use with ReportWORQ and put all the sets against this instead of the default hierarchy.

I’m wrestling with some other issues right now and can’t check in the UI for ReportWORQ 5. Is the use case of sets saved against the non-default hierarchy supported?
TIA

2

@SteveRoweInfocat,

Thanks for the question but I’m not understanding the use case entirely just yet. In ReportWORQ if you choose Enable Bursting for one or more parameters then you can manually create a Burst Set for each report you want to send. This is manual and can be tedious to do in ReportWORQ if there’s a lot. To do it dynamically you can use a single parameter that is set to Create One Report Per Item, then this parameter can be sourced from a Subset, MDX Query or even a typed in list of values. In this case ReportWORQ will dynamically create the burst sets from the parameter’s values. This may not be enough to fulfill the use case though. Do you need to dynamically drive several parameters based on the recipient but also need to do it dynamically?

Thanks,
-Andy

3

In TM1 I need to set up sets to reference in ReportWORQ calls from a TI using the rest API (as I don’t want to set-up Burst sets in ReportWORQ).

If I set up the sets against a hierarchy in PAW how / is it possible to address them in the API call. i.e. soemthing like.
Cost Centre:ReportWORQHierarchy:Report Deck 5
rather than the default / same named hierarchy
Cost Centre:Cost Centre:Report Deck 5

If I can define the sets against a hierarchy then I can hide them from the users of PAW and avoid bloating the sets on the default hierarchy which can be problem over time.

I probably should just try and it let you know…