sql server reporting services: I have parameters that I programmically populate and don't want the user to see.

I remove the value for Prompt in the Paramters dialog in the designer.

After deploying the report I find in the Report Server that Prompt User is
checked and the default prompt lable is the parameter name.

I then remove the checks and the prompt lable and my application now correctly
only prompts for the one or two parameters as it should.

I'm not sure I fully understand what you are saying - but if you are saying
that you deploy a report, and then modify the prompts with the Report
Manager that when you re-deploy the report again that the new prompts appear
not to be respected. Then that is by design.

The design descision is that if a Report has been Administered on teh Report
Server by an Administrator then those settings should take priority over
anything the developer of the report might set, when re-deploying the
report.

Peter Blackburn
Hitchhiker's Guide to SQL Server 2000 Reporting Services
http://www.sqlreportingservices.net


[quoted text, click to view]

Peter,

First off, I accidently posted too soon, fat fingered some strange
keystroke....anyway.

I want to be clear, I'm presenting the parameter prompts in my ASP.Net
application.

I notice that if I query the report server parameters there is an parameter tag,
<promptuser> however there is not a parameter option in the rdl, only
<reportparameter>. I wouldn't know how to take advantage of this tag anyway.

So, contrary to your statement, I have found that for the parameters that my web
application will populate programmically, I have to choose to prompt but remove
the prompt string in the report manager post deployment. Even if I have no
parameter prompt strings in the report parameters, the actual parameter names
are inserted in their place during deployment, overriding the admin settings on
the report server.

With these settings in place the ReportOptions.aspx page correctly prompts for
mimetype and a time period, "Last 7 Days, Last 14 Days etc...." these are the
only prompts that they should see, although there are some 12 parameters for a
given report.

Then if I re-deploy the report all the settings made in the report server are
lost making sure that I cannot depoly reports I must pull using the Upload
option and then check the prompt user check boxes and remove the prompt strings,
other wise the user will be prompted for a market center number, account number,
company name and other sundry parameters that are already determined by their
login and a security breach that they could impersonate someone by entering
other valid parameters.

I get your statement, but in practice it is just the opposite.

TIA

JeffP.....

"Peter Blackburn (www.sqlreportingservices.net)"
[quoted text, click to view]