What I dont understand is it's by design.
For it looks like a bug.
Let's say I have a report with a parameter that has to be entered by the user.
Later on the user decides to have a default value for that paramter.
least once.
"Peter Blackburn (www.sqlreportingservice" wrote:
> Mark,
>
> This behaviour is by design.
> Once a report has been deployed, if you reconfigure the default value for a
> particular parameter through the Report Manager then that will take
> precedence over any default values that you subsequently include in the RDL
> that you may re-deploy.
>
> The rationale behind these kind of things is that the Report Administrator
> is King - if the Report Administrator has manually set something on the
> Report Manager to be overridden then it is not welcome that a Report
> Developer comes along and overwrites such a setting.
>
> Bill and my book gives in-depth treatment of Report Parameters on pages
> 283 - 292 and p286 explains the feature you are experiencing.
>
> Best Wishes.
>
> Peter Blackburn
> Hitchhiker's Guide to SQL Server 2000 Reporting Services
>
www.sqlreportingservices.net >
>
>
> "Mark" <Mark@discussions.microsoft.com> wrote in message
> news:72E5761D-D8FA-42D4-8B03-FC7FDB83C466@microsoft.com...
> >I have a numeric parameter that does not get its default value when I
> >deploy
> > the report. It works fine in report designer preview.
> > Is that a bug?
>
>