Hide Parameters toolbar

How to hide specific parameters from the toolbar:

I use the following link, it hides the whole parameters toolbar.

http://ServerName/reportserver?/PPTReports/rptStatSU&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=false&eStatus=Open&UserName=jSmith

I have two parameters out of that would oike to hide just one of them which is username.

i am using sqlserver 2000 reporting services, i don't see that option hide.

Please does anyone know how to do it.

Thank you very much for the information.

No, in SQL Server 2k you can only hide the report parameters as a whole. In SQL Server you have the possibility to set the parameter to "hidden" or "internal", but if you don′t have the chance of migrating you are stuck to the option to switch of the whole parameter toolbar.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Hide Parameters passed to drillthrough report

hi,
Is it possible to hide parameters passed to drillthrough report?
If yes, How?
regards,
SAchin.yes using rc:parameters=false, when you click on the link the parametes wont
be visible but one small problem (rather big:-) is that it will be visible on
the "address box" in the IE. so if some one goes and removes it then the
parameters will be visile.
Amarnath
"sachin laddha" wrote:
> hi,
> Is it possible to hide parameters passed to drillthrough report?
> If yes, How?
> regards,
> SAchin.
>|||Hi,
Where to set rc:parameters=false so that it appears by defualt in the
report URL?
Can I set it while designing the drillthrough report ?
I am using RS's report manger to view and manager reports.
regards,
Sachin.
Amarnath wrote:
> yes using rc:parameters=false, when you click on the link the parametes wont
> be visible but one small problem (rather big:-) is that it will be visible on
> the "address box" in the IE. so if some one goes and removes it then the
> parameters will be visile.
> Amarnath
> "sachin laddha" wrote:
> > hi,
> >
> > Is it possible to hide parameters passed to drillthrough report?
> > If yes, How?
> >
> > regards,
> > SAchin.
> >
> >|||When you jump to report the parameters section of the report you are jumping
to is not shown. Are you seeing different behavior than this?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sachin laddha" <sachinladdha@.gmail.com> wrote in message
news:1146816702.039630.18710@.e56g2000cwe.googlegroups.com...
> Hi,
> Where to set rc:parameters=false so that it appears by defualt in the
> report URL?
> Can I set it while designing the drillthrough report ?
> I am using RS's report manger to view and manager reports.
> regards,
> Sachin.
>
> Amarnath wrote:
>> yes using rc:parameters=false, when you click on the link the parametes
>> wont
>> be visible but one small problem (rather big:-) is that it will be
>> visible on
>> the "address box" in the IE. so if some one goes and removes it then the
>> parameters will be visile.
>> Amarnath
>> "sachin laddha" wrote:
>> > hi,
>> >
>> > Is it possible to hide parameters passed to drillthrough report?
>> > If yes, How?
>> >
>> > regards,
>> > SAchin.
>> >
>> >
>|||Sorry; I meant for "Jump to URL". A small confusion,
You dont want the parameter section? or the parameters which are passed
through the URL?. Because I meant when you use in the URL
rc:parameters=false the parameter section will not be visible. So let me know
which one you are looking out for.
Amarnath
"sachin laddha" wrote:
> Hi,
> Where to set rc:parameters=false so that it appears by defualt in the
> report URL?
> Can I set it while designing the drillthrough report ?
> I am using RS's report manger to view and manager reports.
> regards,
> Sachin.
>
> Amarnath wrote:
> > yes using rc:parameters=false, when you click on the link the parametes wont
> > be visible but one small problem (rather big:-) is that it will be visible on
> > the "address box" in the IE. so if some one goes and removes it then the
> > parameters will be visile.
> >
> > Amarnath
> >
> > "sachin laddha" wrote:
> >
> > > hi,
> > >
> > > Is it possible to hide parameters passed to drillthrough report?
> > > If yes, How?
> > >
> > > regards,
> > > SAchin.
> > >
> > >
>|||I am using 'Jump to report' option and not 'jump to url' for
navigation.|||Hi Bruce,
Yes, i m seeing the paramters section of the report I am jumping to.
I have set the report to jump and the parameters it take.
Please note that I am seeing the report in VS preview pane and the
reports are not yet deployed on the report server
Please help me out.
regards,
Sachin.|||Problem solved. You are seeing a difference between the development
environment and deployed reports. Jump to Reports with deployed reports does
not show the parameters BUT the user can unhide them. To not have the option
at all to see the parameters you can make the parameters hidden OR you can
use Jump to URL and control the parameter section not to show.
Books Online: hiding parameters
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sachin laddha" <sachinladdha@.gmail.com> wrote in message
news:1147070062.912289.317660@.u72g2000cwu.googlegroups.com...
> Hi Bruce,
> Yes, i m seeing the paramters section of the report I am jumping to.
> I have set the report to jump and the parameters it take.
> Please note that I am seeing the report in VS preview pane and the
> reports are not yet deployed on the report server
> Please help me out.
> regards,
> Sachin.
>

Hide Parameters issue : Where is the "Prompt User" checkbox

I have a problem of hiding a few of my parameters. People are talking
about the SP1 and the "Prompt User" check box. I have SP1 installed.
But I cannot see "Prompt User" checkbox anywhere either in the
ReportManager or the VS.NET Report Designer.
I've been pulling my hair all day. Please let me know how can I get to
that "Prompt User" checkbox. Where is it ?
thanks
Anand SagarThere is not a check box. Make sure your report is highlighted. Click on
the Report option in the menu. Select properties. To set a parameter as
hidden, you have to delete all the text in the "Prompt:" textbox. Once you
do that, you will not see a prompt for the user to enter data for that
parameter. This is all that is needed to "hide" parameters from the end user.
"Anand Sagar" wrote:
> I have a problem of hiding a few of my parameters. People are talking
> about the SP1 and the "Prompt User" check box. I have SP1 installed.
> But I cannot see "Prompt User" checkbox anywhere either in the
> ReportManager or the VS.NET Report Designer.
> I've been pulling my hair all day. Please let me know how can I get to
> that "Prompt User" checkbox. Where is it ?
>
> thanks
> Anand Sagar
>|||There is a "Prompt User" check box in SP1. When you've uploaded your report
to the Report Manager, you'll need to edit the "Parameters" properties.
Check the "Prompt User" check box, then empty out the Prompt String text
box. This allows the parameter to be hidden from the user, but still
updateable by the report.
HTH,
Brian
"bspann" <bspann@.discussions.microsoft.com> wrote in message
news:1F78D438-DDE9-4725-A474-A7BC7FDE880D@.microsoft.com...
> There is not a check box. Make sure your report is highlighted. Click on
> the Report option in the menu. Select properties. To set a parameter as
> hidden, you have to delete all the text in the "Prompt:" textbox. Once
you
> do that, you will not see a prompt for the user to enter data for that
> parameter. This is all that is needed to "hide" parameters from the end
user.
> "Anand Sagar" wrote:
> > I have a problem of hiding a few of my parameters. People are talking
> > about the SP1 and the "Prompt User" check box. I have SP1 installed.
> > But I cannot see "Prompt User" checkbox anywhere either in the
> > ReportManager or the VS.NET Report Designer.
> > I've been pulling my hair all day. Please let me know how can I get to
> > that "Prompt User" checkbox. Where is it ?
> >
> >
> > thanks
> > Anand Sagar
> >|||In Report Manager, select the report, select the properties tab, select the
parameters sub-tab.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"bspann" <bspann@.discussions.microsoft.com> wrote in message
news:1F78D438-DDE9-4725-A474-A7BC7FDE880D@.microsoft.com...
> There is not a check box. Make sure your report is highlighted. Click on
> the Report option in the menu. Select properties. To set a parameter as
> hidden, you have to delete all the text in the "Prompt:" textbox. Once
you
> do that, you will not see a prompt for the user to enter data for that
> parameter. This is all that is needed to "hide" parameters from the end
user.
> "Anand Sagar" wrote:
> > I have a problem of hiding a few of my parameters. People are talking
> > about the SP1 and the "Prompt User" check box. I have SP1 installed.
> > But I cannot see "Prompt User" checkbox anywhere either in the
> > ReportManager or the VS.NET Report Designer.
> > I've been pulling my hair all day. Please let me know how can I get to
> > that "Prompt User" checkbox. Where is it ?
> >
> >
> > thanks
> > Anand Sagar
> >sql

Hide Parameters from User.

Hi,
Is there any way that the parameters passed from the URL is not shown to the users. Making the "Prompt User" unchecked and passing the parameter through the URL gave some error. Is there a work around.
Thanks.
--
Message posted via http://www.sqlmonster.comTry appending this to your URL:
&rc:Parameters=false
"Prashanth Rao via SQLMonster.com" wrote:
> Hi,
> Is there any way that the parameters passed from the URL is not shown to the users. Making the "Prompt User" unchecked and passing the parameter through the URL gave some error. Is there a work around.
> Thanks.
> --
> Message posted via http://www.sqlmonster.com
>

Hide Parameter with SP1

Installed SP1, still finding not possible to hide a parameter. Can someone provide the process please. The parameter is an ID that is send via URL to the report server. I created a Report Parameter for it, then created a queary parameter setting that to the incoming value of the Report Parameter. Help pleaseYou can hide a paremeter after you have deployed your report.
But hiding a parameter disallow you to pass any value to this parameter
through the URL!!!
The parameter is not simply hide to the user, is also completly inaccessible
to the user through any URL, but just available to the administrator to
change the default value of the parameter.
"Eddie" <Eddie@.discussions.microsoft.com> a écrit dans le message de
news:A077DD43-D64A-43DC-9D95-761106A4214E@.microsoft.com...
> Installed SP1, still finding not possible to hide a parameter. Can someone
provide the process please. The parameter is an ID that is send via URL to
the report server. I created a Report Parameter for it, then created a
queary parameter setting that to the incoming value of the Report Parameter.
Help please|||According to another post by Brian Welcker,
"This is onlt supported on the server. In Report Manager, leave the 'prompt
user' checkbox checked but clear our the prompt string. This should not
prompt the user but still allow you to specify them via URL."
with SP1, you should be able to specify in URL
"Jéjé" wrote:
> You can hide a paremeter after you have deployed your report.
> But hiding a parameter disallow you to pass any value to this parameter
> through the URL!!!
> The parameter is not simply hide to the user, is also completly inaccessible
> to the user through any URL, but just available to the administrator to
> change the default value of the parameter.
>
> "Eddie" <Eddie@.discussions.microsoft.com> a écrit dans le message de
> news:A077DD43-D64A-43DC-9D95-761106A4214E@.microsoft.com...
> > Installed SP1, still finding not possible to hide a parameter. Can someone
> provide the process please. The parameter is an ID that is send via URL to
> the report server. I created a Report Parameter for it, then created a
> queary parameter setting that to the incoming value of the Report Parameter.
> Help please
>
>|||From the SP1 Read Me:
4.3.1 Hiding Parameters in a Published Report
In Report Manager, you can now set parameter properties in a way that allows you to achieve two objectives simultaneously:
Hide the parameter fields in a published report.
Specify a parameter value at run time (for example, through a subscription that is used to trigger report execution and delivery).
Previously, the only way to hide a parameter value was to clear the Prompt User check box in the Parameters properties page. However, a side effect of clearing the check box was that you could no longer specify a parameter value for the report at run time. This limitation has been removed. In SP1, you can clear the Prompt User check box to hide the parameter fields and values in the report. Doing so does not introduce restrictions on how you subsequently set the parameter value externally at run time.
"Jéjé" wrote:
> You can hide a paremeter after you have deployed your report.
> But hiding a parameter disallow you to pass any value to this parameter
> through the URL!!!
> The parameter is not simply hide to the user, is also completly inaccessible
> to the user through any URL, but just available to the administrator to
> change the default value of the parameter.
>
> "Eddie" <Eddie@.discussions.microsoft.com> a écrit dans le message de
> news:A077DD43-D64A-43DC-9D95-761106A4214E@.microsoft.com...
> > Installed SP1, still finding not possible to hide a parameter. Can someone
> provide the process please. The parameter is an ID that is send via URL to
> the report server. I created a Report Parameter for it, then created a
> queary parameter setting that to the incoming value of the Report Parameter.
> Help please
>
>|||mmmm...
I'll test this.
maybe this doesn't works for me because I have a default value.
"Eddie" <Eddie@.discussions.microsoft.com> a écrit dans le message de
news:A3AD4330-FF88-46BD-97B8-58AB215F4507@.microsoft.com...
> From the SP1 Read Me:
> 4.3.1 Hiding Parameters in a Published Report
> In Report Manager, you can now set parameter properties in a way that
allows you to achieve two objectives simultaneously:
> Hide the parameter fields in a published report.
> Specify a parameter value at run time (for example, through a subscription
that is used to trigger report execution and delivery).
> Previously, the only way to hide a parameter value was to clear the Prompt
User check box in the Parameters properties page. However, a side effect of
clearing the check box was that you could no longer specify a parameter
value for the report at run time. This limitation has been removed. In SP1,
you can clear the Prompt User check box to hide the parameter fields and
values in the report. Doing so does not introduce restrictions on how you
subsequently set the parameter value externally at run time.
>
> "Jéjé" wrote:
> > You can hide a paremeter after you have deployed your report.
> > But hiding a parameter disallow you to pass any value to this parameter
> > through the URL!!!
> > The parameter is not simply hide to the user, is also completly
inaccessible
> > to the user through any URL, but just available to the administrator to
> > change the default value of the parameter.
> >
> >
> > "Eddie" <Eddie@.discussions.microsoft.com> a écrit dans le message de
> > news:A077DD43-D64A-43DC-9D95-761106A4214E@.microsoft.com...
> > > Installed SP1, still finding not possible to hide a parameter. Can
someone
> > provide the process please. The parameter is an ID that is send via URL
to
> > the report server. I created a Report Parameter for it, then created a
> > queary parameter setting that to the incoming value of the Report
Parameter.
> > Help please
> >
> >
> >|||Ok..
Now i have to create a subscription with specific parameters for this subscription and then i should uncheck Promt User checkbox?
Is that right?
The result report i'll use the parameter without problems?
"Eddie" wrote:
> From the SP1 Read Me:
> 4.3.1 Hiding Parameters in a Published Report
> In Report Manager, you can now set parameter properties in a way that allows you to achieve two objectives simultaneously:
> Hide the parameter fields in a published report.
> Specify a parameter value at run time (for example, through a subscription that is used to trigger report execution and delivery).
> Previously, the only way to hide a parameter value was to clear the Prompt User check box in the Parameters properties page. However, a side effect of clearing the check box was that you could no longer specify a parameter value for the report at run time. This limitation has been removed. In SP1, you can clear the Prompt User check box to hide the parameter fields and values in the report. Doing so does not introduce restrictions on how you subsequently set the parameter value externally at run time.

Hide parameter toolbar and send par via querystring?

Hide parameter toolbar and send par via querystring?
I have some stored proceures that receive some parameters and output some
querys. I dont want the user to select parameters because I need to gice
those parameters via query string from My Applications
How can I achieve tha?
--
LUIS ESTEBAN VALENCIA
MICROSOFT DCE 3.
MIEMBRO ACTIVO DE ALIANZADEV
http://spaces.msn.com/members/extremed/Luis,
Check out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_urlaccess_959e.asp
Adrian M.
"Luis Esteban Valencia" <luisvalen@.haceb.com> wrote in message
news:%23n13jSW$EHA.1400@.TK2MSFTNGP11.phx.gbl...
> Hide parameter toolbar and send par via querystring?
>
> I have some stored proceures that receive some parameters and output some
> querys. I dont want the user to select parameters because I need to gice
> those parameters via query string from My Applications
>
> How can I achieve tha?
>
> --
> LUIS ESTEBAN VALENCIA
> MICROSOFT DCE 3.
> MIEMBRO ACTIVO DE ALIANZADEV
> http://spaces.msn.com/members/extremed/
>

Hide parameter for some users

I'm trying to decide whether I can use sql reports for my application, and
the main problem I've run into thus far is that my available parameters need
to change based on the user who is running the report. For instance,
low-level users should only be able to see data about themselves, whereas
managers should be able to select from a drop-down list of all users. Is
there any way to set the user prompt/visibility for a parameter based on the
role of the person running the report?The easiest way I can think of to manage this is to have two versions of the
same report. With the regular version, pass =User!UserID into the query
parameter. In the manager's version, populate the same parameter from a
drop-down list. Then set different permissions when you deploy the reports.
If you need to do it in a single report, you might be able to write some
custom code to pass in flags to the query and work out the difference
between managers and employees in your data source query.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"jgephart" <jgephart@.discussions.microsoft.com> wrote in message
news:36979870-6D83-4C49-B1E6-88D8CBC51678@.microsoft.com...
> I'm trying to decide whether I can use sql reports for my application, and
> the main problem I've run into thus far is that my available parameters
> need
> to change based on the user who is running the report. For instance,
> low-level users should only be able to see data about themselves, whereas
> managers should be able to select from a drop-down list of all users. Is
> there any way to set the user prompt/visibility for a parameter based on
> the
> role of the person running the report?|||Thanks, Jeff. This will affect a whole series of reports, so I don't really
want to maintain separate versions. I think I'm going to be able to go with
passing in User!UserID to the query that builds the drop-down list of users.
I can't hide the drop-down list, but at least I can make sure it's only
populated with a single user if that user doesn't have permission to see
other people's data.
"Jeff A. Stucker" wrote:
> The easiest way I can think of to manage this is to have two versions of the
> same report. With the regular version, pass =User!UserID into the query
> parameter. In the manager's version, populate the same parameter from a
> drop-down list. Then set different permissions when you deploy the reports.
> If you need to do it in a single report, you might be able to write some
> custom code to pass in flags to the query and work out the difference
> between managers and employees in your data source query.
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---|||To protect it on the back side (from someone simply altering the URL to look
at someone else's data) you could always create a permissions table that
contains all of the usernames that each user is allowed to look at, and have
that table always be in the source query join, with User!UserID passed into
the query. We're doing a variation on this (a join to a parameterized UDF)
for our data security solution.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"jgephart" <jgephart@.discussions.microsoft.com> wrote in message
news:F5C7BDD7-4F0D-488C-80CB-7F81201B08A4@.microsoft.com...
> Thanks, Jeff. This will affect a whole series of reports, so I don't
> really
> want to maintain separate versions. I think I'm going to be able to go
> with
> passing in User!UserID to the query that builds the drop-down list of
> users.
> I can't hide the drop-down list, but at least I can make sure it's only
> populated with a single user if that user doesn't have permission to see
> other people's data.
>
> "Jeff A. Stucker" wrote:
>> The easiest way I can think of to manage this is to have two versions of
>> the
>> same report. With the regular version, pass =User!UserID into the query
>> parameter. In the manager's version, populate the same parameter from a
>> drop-down list. Then set different permissions when you deploy the
>> reports.
>> If you need to do it in a single report, you might be able to write some
>> custom code to pass in flags to the query and work out the difference
>> between managers and employees in your data source query.
>> --
>> Cheers,
>> '(' Jeff A. Stucker
>> \
>> Business Intelligence
>> www.criadvantage.com
>> ---|||You could use linked reports instead, possibly in conjunction with the
My Reports feature. Linked reports are effectively shortcuts to a
report.
But, the nice touch is that you can set the parameters to behave a bit
differently, for instance there is a prompt user check box on each
parameter in the linked reports properties. This doesn't affect the
original report. If you update the original, the linked report will
reflect these changes too. Security can be set completely independantly
too.
Chris
Jeff A. Stucker wrote:
> To protect it on the back side (from someone simply altering the URL
> to look at someone else's data) you could always create a permissions
> table that contains all of the usernames that each user is allowed to
> look at, and have that table always be in the source query join, with
> User!UserID passed into the query. We're doing a variation on this
> (a join to a parameterized UDF) for our data security solution.sql