They’re all the same report, just with different parameters.
Since we’re going to be upgrading to BOXI soon, I thought I’d try and fix this mess.
I’m a .NET developer, and I was wondering if what I was thinking was even possible.
We have Appworx, and I was thinking of creating a .NET app that would loop through a LOV and use just one physical report to generate all the instances.
So, it’s a .NET job triggered by Appworx that loops variables through a report.
This is the sort of thing that Broadcast Agent was designed to do, but you can just as easily do it from a Macro in full client (assuming these are full client reports), or an asp/jsp script for webi docs.
I looked into bursting, but it initially appears that bursting is more about security (who can see what data in the report) then actually “looping” the reports.
Also, from what little I can gather, it sounds like you need to use Desktop Intelligence with bursting?
Did you move further with this. I am trying hard in looking into bursting capabilities using DeskI however still cannot get a definitive picture. I will appreciate if you can share ideas.
Instead, I just wrote a script that creates a large directory of subdirectories, and places “new” reports in each of those with appropriate parameters.
I’m attaching a zip file with 3 asp files in it.
global.asp & functions.asp are universal pages that i include on a bunch of other pages. you can probably merge the two if you wanted.
functions.asp has a bunch of useful functions:
ReturnReportID
ReturnFolderID
AddFolder
AddReport
rcreports.asp is basically a loop to call those functions and pass in specific parameters.
I documented farily well I think, but if you need to know more let me know. scripts.zip (3.0 KB)