Reusing Report Parameters

Let's say I have 10 reports in a project where each report requires a
"drop down list" type of filter. We'll call this filter (report
parameter) "Product Type" and is a populated from a stored proc.
In order to put this Product type parameter on each report, do I need
to define the dataset which references the stored proc in each report?
Or is there a way to define the dataset one time, in some sort of
shared area, where it can be simply referenced by each of the reports.
Any suggestions on how to avoid duplicating prodcedure calls?
TIA
RobI too wish for the same feature. I would like to be able to define a global
dataset just like having a global data source defined. It is not feature of
this version. At least by having a stored procedure you have put the logic
in one place.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rob Hoeting" <rhoeting@.hotmail.com> wrote in message
news:5a283851.0410190435.21012bf3@.posting.google.com...
> Let's say I have 10 reports in a project where each report requires a
> "drop down list" type of filter. We'll call this filter (report
> parameter) "Product Type" and is a populated from a stored proc.
> In order to put this Product type parameter on each report, do I need
> to define the dataset which references the stored proc in each report?
> Or is there a way to define the dataset one time, in some sort of
> shared area, where it can be simply referenced by each of the reports.
> Any suggestions on how to avoid duplicating prodcedure calls?
> TIA
> Rob|||Hello Rob,
Kind of. There are a few techniques I can think of that might help you and
partially solve the problem:-
The first is to view the Report in Code View - which will show you the RDL
for the report - you can then cut, copy and paste sections to the Toolbox -
and then when you are in your next report you can copy the sections back in.
I often work directly with the RDL because it is a lot quicker that messing
around with the mouse... but then I edit my web pages in Visual Notepad too!
The second thing you can do, is that you can create a Report Template.
Chapter 9 of the Hitchhiker's Guide to SQL Server 2000 Reporting Services,
shows how to create Report Templates and the various behind the scenes steps
that you take to set-up configuration files.
Peter Blackburn
Hitchhiker's Guide to SQL Server 2000 Reporting Services
www.sqlreportingservices.net
"Rob Hoeting" <rhoeting@.hotmail.com> wrote in message
news:5a283851.0410190435.21012bf3@.posting.google.com...
> Let's say I have 10 reports in a project where each report requires a
> "drop down list" type of filter. We'll call this filter (report
> parameter) "Product Type" and is a populated from a stored proc.
> In order to put this Product type parameter on each report, do I need
> to define the dataset which references the stored proc in each report?
> Or is there a way to define the dataset one time, in some sort of
> shared area, where it can be simply referenced by each of the reports.
> Any suggestions on how to avoid duplicating prodcedure calls?
> TIA
> Rob

Re-use filter

I have a chunk of SQL that is use if a particular report needs to have
a point in time parameter. Is there any way to store this code so any
report in the solution has access to it? I don't want any business
users that develop reports to have to type all the SQL in every time.
Any thoughts?You could create a custom assembly that returned this chunk of SQL and then
construct your commands through an expression that calls your custom
assembly.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Austin S" <austinswope@.gmail.com> wrote in message
news:b68c96f7.0409281425.27324a81@.posting.google.com...
>I have a chunk of SQL that is use if a particular report needs to have
> a point in time parameter. Is there any way to store this code so any
> report in the solution has access to it? I don't want any business
> users that develop reports to have to type all the SQL in every time.
> Any thoughts?