Hi All
Long time no see, I wasn’t even aware BOBJ was still going! 
I’ve been reading about publications and single pass bursting, but I’m not sure its what I need, and hopefully you may be able to advise.
We have a report that needs to be generated once for each value in a dimension [Provider]
All of the reports need to be delivered to a common location (probably an Outlook mailbox) as Excel.
There is no requirement to deliver different outputs to different users (which is what profiles do I believe)
Just to generate an instance of the report for each [Provider]
We’re currently on 4.2 (last SP) but have 4.3 SP5 in the wings that I’m trying to get ready to go live asap (writing FIORI guidance is killing me currently!)
Is this possibly where we’d use one report to generate the [Provider] values and use it as a dynamic input for a prompt in the main report, so it loops through each value in turn?
Thanks for any pointers!
No, you cannot use it as input, but instead as dynamic output.
Read all the values into one report and separate the content/pages (your dimension) with sections.
The other report can be used to set the target and publish each section to a different file or mail-receiver.
Actually, I did a bit more searching and it appears you can make publications do this but its a bit unintuitive to set up. It’s a very old post, but I managed a basic test in 4.2 last night and it appears to work still.
Webi dynamic schedule with prompt - sdk development - BusinessObjects Board
Do you have any more info/pointers/keywords to search for about how this is done using sections as you’ve described?
Create the target WebI report with all content for your recipients. Insert your dimension into a section so that your content is split across separate pages for each recipient (check that the “Each section on a new page” parameter is enabled).
Load all data from your source into the report and check that the content is displayed as desired for each dimension.
Create a second WebI report (it can be based e.g. on an Excel table) that contains two columns (dimension fieldname and target name mapping). This is the mapping between your dimension and e.g. the target file name or an email recipient address.
In the publication, you can map the dimension fieldname of the first report to the fieldname of the second report and use column 2 of the second report as the placeholder for the file name or email recipient.