here is an example of this bug at work.. (i am using RS SP1)
1) upload this report into report manager
2) - RUN THE Report, and notice that the 2nd parameter called
'defaultparam' gets set to the date, and it works.. (all the report
does is show this parameter)
3) - go to the parameter editing section of hte report in report
manager
4) - change something UNRELELATED to defaultparam - for instance the
PROMPT of the firstparameter - dummyparam, and then APPLY
5) - go back to the report - and "defaultparam" nolonger calculates the
date (the default parameter expression in the report)
conclusion, report manager not only updates the parameters you change,
(as it should to give the administrator ability to), it erroneously
updates all the parameters..
also i notice that query based default (foir single value, rather than
name,value) don't show up in report manager as "query based" (and thus also
sucumb to this bug")
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefini..."xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<Top>0.125in</Top>
<rd:DefaultName>textbox1</rd:DefaultName>
<Height>0.25in</Height>
<Width>1in</Width>
<CanGrow>true</CanGrow>
<Value>=Parameters!defaultparam.Value</Value>
<Left>0.25in</Left>
</Textbox>
</ReportItems>
<Style />
<Height>2in</Height>
</Body>
<TopMargin>1in</TopMargin>
<Width>6.5in</Width>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportÂID>
<BottomMargin>1in</BottomMargin>
<ReportParameters>
<ReportParameter Name="dummyparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>dummyparameter</Prompt>
</ReportParameter>
<ReportParameter Name="defaultparam">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>=Format(DateTime.Now,"d")</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>defaultparam</Prompt>
</ReportParameter>
<ReportParameter Name="nextparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Report_Parameter_2</Prompt>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>please excuse the double posts, i thought i was putting it on a private
newsgroup at msdn subscribers|||This is a known limitation of the report manager report parameter page.
This issue should be fixed in Yukon.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> please excuse the double posts, i thought i was putting it on a private
> newsgroup at msdn subscribers|||is there a way to make a 'hidden writeable (not read only) parameter' other
than changing in in report manager (which messes up the other default ones?)
because in report designer you can't make it this way, you can omit the
prompt , but then its hidden but gives you READONLY parameter errors if
trying to set it in the URL..
maybe there is a script that uses the webservice or something?
"Daniel Reib [MSFT]" wrote:
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> > please excuse the double posts, i thought i was putting it on a private
> > newsgroup at msdn subscribers
>
>|||There is actually a way to achieve a hidden parameter in SP1 and in the
upcoming SP2 through report designer: specify just at least one blank as
report parameter prompt and publish to the report server.
Note: the parameter will still be prompted in designer preview, but it will
not be prompted in the viewer of report manager.
The next version (RS2005) will have a better solution for managing hidden
parameters (also through the SOAP API and report manager).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:1BCA549E-DD3D-4754-A1D1-6077EA3D3243@.microsoft.com...
> is there a way to make a 'hidden writeable (not read only) parameter'
> other
> than changing in in report manager (which messes up the other default
> ones?)
> because in report designer you can't make it this way, you can omit the
> prompt , but then its hidden but gives you READONLY parameter errors if
> trying to set it in the URL..
> maybe there is a script that uses the webservice or something?
>
> "Daniel Reib [MSFT]" wrote:
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> > please excuse the double posts, i thought i was putting it on a private
>> > newsgroup at msdn subscribers
>>|||nice.. just a space instead of a blank.. well at least i can control it
completely from the RDL, its a big releif, i think i need to start a site
with Questions and Answers for these bizarre things in RS
"Robert Bruckner [MSFT]" wrote:
> There is actually a way to achieve a hidden parameter in SP1 and in the
> upcoming SP2 through report designer: specify just at least one blank as
> report parameter prompt and publish to the report server.
> Note: the parameter will still be prompted in designer preview, but it will
> not be prompted in the viewer of report manager.
>|||Daniel,
Would there happen to be a published list of 'known limitations' for RS SP1,
or do we just have to figure these things out as we come upon them?
--
Adrian M.
MCP
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>|||Unfortunately, such a site does not exist. We are so busy fixing them (and
adding new ones <g>) that we haven't had time to create something like this.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
news:eGTLpKcFFHA.1292@.TK2MSFTNGP10.phx.gbl...
> Daniel,
> Would there happen to be a published list of 'known limitations' for RS
> SP1, or do we just have to figure these things out as we come upon them?
> --
> Adrian M.
> MCP
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment