Dislpay Report Parameters selectively?

I was wondering if there is a way I can selective display report parameters?
For example, I have one parameters that lets the user select a report type.
If the user selects 'Daily' I want to display the report parameter that
allows the user select a date. On the other hand if the user selects
'Monthly' I want to display a drop down list that has all months preloaded.
I do not want the dropdown list that contains months to show up if the user
wants to run a 'Daily' report.
Any help would be much appreciated!
TIA
VinayPresuming that you are also able to display a drop-down list of available
dates if the user selects 'Daily' then the way I would do this is to have a
dataset using a stored procedure which takes the Daily/Monthly parameter and
generates the drop-down list accordingly.
HTH,
magendo_man
"Vinay" wrote:
> I was wondering if there is a way I can selective display report parameters?
> For example, I have one parameters that lets the user select a report type.
> If the user selects 'Daily' I want to display the report parameter that
> allows the user select a date. On the other hand if the user selects
> 'Monthly' I want to display a drop down list that has all months preloaded.
> I do not want the dropdown list that contains months to show up if the user
> wants to run a 'Daily' report.
> Any help would be much appreciated!
> TIA
> Vinay
>
>

Disbling parameters pased in URL

Hi,
I'm passing in parameters via the URL. Is there a way to disable some
parameters so users can't change them once the report is displayed in the
browser and ready to run? I don't see it in 2000, but maybe it's in 2005
which I haven't purchased yet.
thanks,
-TrishHave you tried making the parameters hidden?
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Trishmi" wrote:
> Hi,
> I'm passing in parameters via the URL. Is there a way to disable some
> parameters so users can't change them once the report is displayed in the
> browser and ready to run? I don't see it in 2000, but maybe it's in 2005
> which I haven't purchased yet.
> thanks,
> -Trish|||I'm not sure how to make the parameters hidden on the report viewer once the
report is launched.
Here is how I'm launching my report from a .aspx file:
<FORM id="frmRender"
action="http://myreporserver/reportserver?<%=Request("RPT")%>" method="post">
<INPUT type="hidden" name="rs:Command" value="Render">
<INPUT type="hidden" name="rc:LinkTarget" value="main">
<INPUT type="hidden" name="rs:Format" value="HTML4.0">
<input type="hidden" name="db" value=<%=Session("HostDB")%>>
<input type="hidden" name="Company" value=<%=Session("CompanyName")%>>
</FORM>
Once it launches, the DB and Company parameters show in the toolbar. I'd
like to disable those. I can't hide the whole toolbar because there will be
parameters that require the user to select from a dropdownlistbox.
thanks,
-Trish
"Wayne Snyder" wrote:
> Have you tried making the parameters hidden?
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
>
> "Trishmi" wrote:
> > Hi,
> >
> > I'm passing in parameters via the URL. Is there a way to disable some
> > parameters so users can't change them once the report is displayed in the
> > browser and ready to run? I don't see it in 2000, but maybe it's in 2005
> > which I haven't purchased yet.
> >
> > thanks,
> > -Trish

Disabling One Input Parameter...?

Hi All,
I am creating a report which calls for four input parameters A, B, C, and D.
How can I disable D if A, B, and C are selected or disable C if A, B, and D
are selected?
Thx, ChuckThis is not supported. The only way to achieve this right now is to
implement your own front end application which handles the parameter UI and
then e.g. uses SOAP or URL-access to pass the "validated" parameters to the
report server.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:32F07069-7C11-4608-9E86-68796ED25A99@.microsoft.com...
> Hi All,
> I am creating a report which calls for four input parameters A, B, C, and
> D.
> How can I disable D if A, B, and C are selected or disable C if A, B, and
> D
> are selected?
> Thx, Chuck|||Set a table up in your database called "NILL" with a column called "NILL"
as well. Use the from query section in the report parameters and create a
query which points to this table. Set your Non-queried Default value to
NILL.
Create a dataset for each report parameter. Some duplication, but is quick
and it works. Have done it for database table and columns names where one
or more can be selected and the column info is passed back as a results
alias and is returned independently of the other report parameters.
Eg. DBTableNames
Select Name, Id
From sysobjects where xtype ='U'And ID <> 197555541
Order by Name
DBTablesColNames relys on a tablename to be selected before the report will
allow the selection of a column
Select Name
From syscolumns
Where id = (Select Id
From sysobjects
Where xtype = 'U' AND Name = @.DBName)
** @.DBName = Parameters!TableParameter.Value **
I had to implement custom code in order for this to be of benefit.
Eg. Dataset CustomSQL
= Code.GetSQL(Parameters!TableParameter.Value, Parameters!
ColumnParameter.Value, Parameters!EndDate.Value, Parameters!Interval.Value,
Parameters!NoOfIntervals.Value)
As you can see from the dataset CustomSQL this is one of my so called
"Adhoc Reports" which allows the user to choose a database table and one of
its columns with a given date, an iterval (ie. Daily, Monthly etc), and the
No. of intevals. I have three tables on the report page that each call this
dataset passing in their own report parameters.
Note you have to manually set the name and database feild under "Fields" to
Results to get any data back

Disabling AutoRendering for Reports with Default Parameters

I have a report with default parameters. Every time the report is selected,
it automatically renders the report using the defaults. Is there any way to
disable the AutoRendering feature so my users can choose to override the
report's defaults and then render the report manually?
--
Jay P. Meredith
Senior Software Engineer
Columbia Helicopters, Inc.
PO Box 3500
Portland, OR 97208Just a stab, but maybe worth trying... What if you add a hidden parameter
which has no default value, and is not used... That might prevent
auto-render, and force the user to select the view report button... ( I
don't know what potential bad side effects might occur tho...)
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
>I have a report with default parameters. Every time the report is
>selected,
> it automatically renders the report using the defaults. Is there any way
> to
> disable the AutoRendering feature so my users can choose to override the
> report's defaults and then render the report manually?
> --
> Jay P. Meredith
> Senior Software Engineer
> Columbia Helicopters, Inc.
> PO Box 3500
> Portland, OR 97208|||Wayne,
A hidden parameter with no default value will cause the report not to render
at all. After all, if it has no default, it has to be told what its value
is. And if the user can't see it to choose a value, then the report will
just sit there, waiting for input.
The only way I've found against AutoRender when the report is first open is
to leave one of my parameters with no default, forcing the user to make a
choice on it.
BLARGH... It would be nice if RS was old enough that someone else had all
the answers and we didn't have to be the ones to find out the answers the
hard way. @.=/
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Wayne Snyder" wrote:
> Just a stab, but maybe worth trying... What if you add a hidden parameter
> which has no default value, and is not used... That might prevent
> auto-render, and force the user to select the view report button... ( I
> don't know what potential bad side effects might occur tho...)
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
> news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
> >I have a report with default parameters. Every time the report is
> >selected,
> > it automatically renders the report using the defaults. Is there any way
> > to
> > disable the AutoRendering feature so my users can choose to override the
> > report's defaults and then render the report manually?
> > --
> > Jay P. Meredith
> > Senior Software Engineer
> > Columbia Helicopters, Inc.
> > PO Box 3500
> > Portland, OR 97208
>
>|||Leaving one or more unhidden parameters without defaults seems to be the best
compromise. In defaulting all parameters, I was trying to save the user a
few keystrokes. Thanks.
--
Jay P. Meredith
Senior Software Engineer
Columbia Helicopters, Inc.
PO Box 3500
Portland, OR 97208
"Catadmin" wrote:
> Wayne,
> A hidden parameter with no default value will cause the report not to render
> at all. After all, if it has no default, it has to be told what its value
> is. And if the user can't see it to choose a value, then the report will
> just sit there, waiting for input.
> The only way I've found against AutoRender when the report is first open is
> to leave one of my parameters with no default, forcing the user to make a
> choice on it.
> BLARGH... It would be nice if RS was old enough that someone else had all
> the answers and we didn't have to be the ones to find out the answers the
> hard way. @.=/
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the back?
> @.=)
>
> "Wayne Snyder" wrote:
> > Just a stab, but maybe worth trying... What if you add a hidden parameter
> > which has no default value, and is not used... That might prevent
> > auto-render, and force the user to select the view report button... ( I
> > don't know what potential bad side effects might occur tho...)
> >
> > --
> > Wayne Snyder, MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > www.mariner-usa.com
> > (Please respond only to the newsgroups.)
> >
> > I support the Professional Association of SQL Server (PASS) and it's
> > community of SQL Server professionals.
> > www.sqlpass.org
> >
> > "Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
> > news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
> > >I have a report with default parameters. Every time the report is
> > >selected,
> > > it automatically renders the report using the defaults. Is there any way
> > > to
> > > disable the AutoRendering feature so my users can choose to override the
> > > report's defaults and then render the report manually?
> > > --
> > > Jay P. Meredith
> > > Senior Software Engineer
> > > Columbia Helicopters, Inc.
> > > PO Box 3500
> > > Portland, OR 97208
> >
> >
> >|||Always glad to be of assistance. @.=)
Catadmin
"Jay Meredith" wrote:
> Leaving one or more unhidden parameters without defaults seems to be the best
> compromise. In defaulting all parameters, I was trying to save the user a
> few keystrokes. Thanks.
> --
> Jay P. Meredith
> Senior Software Engineer
> Columbia Helicopters, Inc.
> PO Box 3500
> Portland, OR 97208
>
> "Catadmin" wrote:
> > Wayne,
> >
> > A hidden parameter with no default value will cause the report not to render
> > at all. After all, if it has no default, it has to be told what its value
> > is. And if the user can't see it to choose a value, then the report will
> > just sit there, waiting for input.
> >
> > The only way I've found against AutoRender when the report is first open is
> > to leave one of my parameters with no default, forcing the user to make a
> > choice on it.
> >
> > BLARGH... It would be nice if RS was old enough that someone else had all
> > the answers and we didn't have to be the ones to find out the answers the
> > hard way. @.=/
> >
> > Catadmin
> > --
> > MCDBA, MCSA
> > Random Thoughts: If a person is Microsoft Certified, does that mean that
> > Microsoft pays the bills for the funny white jackets that tie in the back?
> > @.=)
> >
> >
> > "Wayne Snyder" wrote:
> >
> > > Just a stab, but maybe worth trying... What if you add a hidden parameter
> > > which has no default value, and is not used... That might prevent
> > > auto-render, and force the user to select the view report button... ( I
> > > don't know what potential bad side effects might occur tho...)
> > >
> > > --
> > > Wayne Snyder, MCDBA, SQL Server MVP
> > > Mariner, Charlotte, NC
> > > www.mariner-usa.com
> > > (Please respond only to the newsgroups.)
> > >
> > > I support the Professional Association of SQL Server (PASS) and it's
> > > community of SQL Server professionals.
> > > www.sqlpass.org
> > >
> > > "Jay Meredith" <JayMeredith@.discussions.microsoft.com> wrote in message
> > > news:5E0D389A-8EE3-417B-A658-8DFCBD01D483@.microsoft.com...
> > > >I have a report with default parameters. Every time the report is
> > > >selected,
> > > > it automatically renders the report using the defaults. Is there any way
> > > > to
> > > > disable the AutoRendering feature so my users can choose to override the
> > > > report's defaults and then render the report manually?
> > > > --
> > > > Jay P. Meredith
> > > > Senior Software Engineer
> > > > Columbia Helicopters, Inc.
> > > > PO Box 3500
> > > > Portland, OR 97208
> > >
> > >
> > >

Disabled or Locked Date Parameters

Hi
I'm fairly new to Reporting Services. We have three or four parameters in
our reports. The FirstDate and LastDate parameters (datetime) are disabled
or locked until we fill in information in the other parameter fields. If the
date parameters are first in the list, they are not disabled or locked. But
we would like them to be last most of the time. Is there a way to "unlock"
them so they are enabled when the report is run instead of having to fill out
the other parameters first?
TIA
MarieJOn Apr 19, 8:08 am, MarieJ <Mar...@.discussions.microsoft.com> wrote:
> Hi
> I'm fairly new to Reporting Services. We have three or four parameters in
> our reports. The FirstDate and LastDate parameters (datetime) are disabled
> or locked until we fill in information in the other parameter fields. If the
> date parameters are first in the list, they are not disabled or locked. But
> we would like them to be last most of the time. Is there a way to "unlock"
> them so they are enabled when the report is run instead of having to fill out
> the other parameters first?
> TIA
> MarieJ
As long as they are not dependent on preceding report parameters, they
should not appear locked. Make sure that the datasets that are
sourcing the parameters are not dependent on the wrong parameters
themselves. To check this, select the Data tab and select the correct
Dataset name from the drop-down list and select the Edit Selected
Dataset [...] button and then check the parameter mappings of the
dataset via the Parameters tab. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

disable automatic execution and rendering

I use asp.net page to view the reports. Some of my reports take parameters
and I set them default to '%' as while cards.
When a report link is clicked, the report is executed and rendered when the
new page is open. Some of them returns really quite some records so it takes
a while to have the page rendered.
Is there a setting somewhere that the reports are not executed and rendered
when the hosting page is open and the process will start only when the "View
Report" button is clicked?
Thank you.You need at least one parameter to not have a default. Otherwise it renders
automatically. I would prefer this behaviour to be different. I haven't
checked 2005 to see if it has changed but this is the way it works in 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ZWeng" <ZWeng@.discussions.microsoft.com> wrote in message
news:32F0A618-C751-479F-9FE1-7CF542E71A35@.microsoft.com...
>I use asp.net page to view the reports. Some of my reports take parameters
> and I set them default to '%' as while cards.
> When a report link is clicked, the report is executed and rendered when
> the
> new page is open. Some of them returns really quite some records so it
> takes
> a while to have the page rendered.
> Is there a setting somewhere that the reports are not executed and
> rendered
> when the hosting page is open and the process will start only when the
> "View
> Report" button is clicked?
> Thank you.
>|||It still works the same way in RS 2005... It would be nice to have a
No-Autorender flag...
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Bruce L-C [MVP]" wrote:
> You need at least one parameter to not have a default. Otherwise it renders
> automatically. I would prefer this behaviour to be different. I haven't
> checked 2005 to see if it has changed but this is the way it works in 2000.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ZWeng" <ZWeng@.discussions.microsoft.com> wrote in message
> news:32F0A618-C751-479F-9FE1-7CF542E71A35@.microsoft.com...
> >I use asp.net page to view the reports. Some of my reports take parameters
> > and I set them default to '%' as while cards.
> >
> > When a report link is clicked, the report is executed and rendered when
> > the
> > new page is open. Some of them returns really quite some records so it
> > takes
> > a while to have the page rendered.
> >
> > Is there a setting somewhere that the reports are not executed and
> > rendered
> > when the hosting page is open and the process will start only when the
> > "View
> > Report" button is clicked?
> >
> > Thank you.
> >
> >
>
>

Disable and/or Hide Parameters

Is it possible to conditionally disable or hide parameter prompts, depending
on other already selected parameter values? For example, if I have two
parameters p1 and p2, is it possible to somehow disable or hide p2 if
P1="Yes"? Also, is it possible to conditinally set the default value of a
parameter, based on the user-selected value of another parameter? for ex: If
P1="YES", set default value of P2
to "2005"
Thanks in advanceSorry, conditionally hiding parameters dependent on other parameters values
is not supported natively at this point. The closest you can get right now
is to write your own custom parameter application that knows about your
business logic and once all parameters are satisfied, you use a SOAP call
(or URL access) to trigger the rendering of the report.
Adding the ability to conditionally hide parameters is a good suggestion and
it is under consideration for future releases.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"isaak" <isaak.peretsman at usa.dupont.com (no spam)> wrote in message
news:F0F8CE1D-6A38-4821-AEBA-30EA647CA913@.microsoft.com...
> Is it possible to conditionally disable or hide parameter prompts,
> depending
> on other already selected parameter values? For example, if I have two
> parameters p1 and p2, is it possible to somehow disable or hide p2 if
> P1="Yes"? Also, is it possible to conditinally set the default value of a
> parameter, based on the user-selected value of another parameter? for ex:
> If
> P1="YES", set default value of P2
> to "2005"
> Thanks in advance