I have a set of common reports which I run on a nightly snap shot just fine.
I would like to run a snap shot on these same reports passing a customer_id parameter to override the default customer_id already in the report.
I know one way around this is to create a linked report from the core reports and change the customer_id parameter there but I would rather not maintain several thousand linked reports folders or have to go through and create a new one every time we have a new customer.
So is there a way I can send a parameter through a Snap Shot or some other way I could do this that I have not thought of?
You can't really dynamically provide a per-snapshot parameter the way you describe it. One thing you could do (which has its own implicit drawbacks) is to create your snapshots with default paramter values that will NOT do any fitering at all. You essentially save a giant snapshot of ALL your data.
Then, when your users request the snapshot, you implement filtering on the report server itself (instead of on the SQL side) by utilizing a filter on the dataset or data region itself -- The obvious drawback is that you're bringing tons of unnecessary data across the wire to be filtered at SSRS....
|||Russell Christopher - msft wrote: Then, when your users request the snapshot, you implement filtering on the report server itself (instead of on the SQL side) by utilizing a filter on the dataset or data region itself -- The obvious drawback is that you're bringing tons of unnecessary data across the wire to be filtered at SSRS....
Ok, this is what I plan on doing but i've been all over the net looking for how to do exactly this, could someone explain?
|||We have a similar requirement for creating snapshots and we are going to write a console application that will do all of our schedule runs and call the SetReportParameters() method along with CreateReportHistorySnapshot() right after it.
This solves the issues with runs for all data, which our security would never allow, even if we guaranteed that the filters would work.
No comments:
Post a Comment