From: InvalidLastName on
Hi,
I accidentally found out by adding "<StreamRoot>your stream root goes here</StreamRoot>" into DeviceInfo will resolve this issue.


For example:
This won't work
string devInfo = @"<DeviceInfo><Toolbar>False</Toolbar><Section>1</Section><HTMLFragment>False</HTMLFragment></DeviceInfo>";

But this will make toggle item work

string devInfo = @"<DeviceInfo><StreamRoot></StreamRoot><Toolbar>False</Toolbar><Section>1</Section><HTMLFragment>False</HTMLFragment></DeviceInfo>";

Hope this will help

However,I do notice the device info for html output described in BOL seems not work as expected
http://msdn2.microsoft.com/en-us/library/ms155395.aspx

For example:
from BOL
HTMLFragment
Indicates whether an HTML fragment is created in place of a full HTML document. An HTML fragment includes the report content in a TABLE element and omits the HTML and BODY elements. The default value is false. If you are rendering to HTML using the Render method of the SOAP API, you need to set this device information to true if you are rendering a report with images. Rendering using SOAP with the HTMLFragment property set to true creates URLs containing session information that can be used to properly request images. The images must be uploaded resources in the report server database. (ILN: I am seeing different behavior ...)



Toolbar
Indicates whether to show or hide the toolbar. The default of this parameter is true. If the value of this parameter is false, all remaining options (except the document map) are ignored. If you omit this parameter, the toolbar is automatically displayed for rendering formats that support it.

The Report Viewer toolbar is rendered when you use URL access to render a report. The toolbar is not rendered through the SOAP API. However, the Toolbar device information setting affects the way that the report is displayed when using the SOAP Render method. If the value of this parameter is true when using SOAP to render to HTML, only the first section of the report is rendered. If the value is false, the entire HTML report is rendered as a single HTML page. (ILN: I am seeing different behavior ...)




- InvalidLastName


"Dave" <thatsastounding(a)gmail.com> wrote in message news:1152281172.634321.13310(a)p79g2000cwp.googlegroups.com...
> Hi. I have the same exact issue as the above two people and I am
> anxiously awaiting your reply. Whenever we do a webservice.ToggleItem,
> the report session seems to get lost. The issue occurs in SP1 of Sql
> Server 2005. We have the same exact code running on a server without
> SP1 and ToggleItem works perfectly.
>
> Any help is appreciated, thank you.
>
>
>
> Dave
>
>
>
> Wei Lu [MSFT] wrote:
>> Hi Spamme,
>>
>> I have done some researching on this issue. I found that the session
>> created in the Report Temp database by LoadReportDefinition method will be
>> different with the LoadReport method.
>>
>> This issue is most like that the LoadReportDefinition method does not hold
>> the report session.
>>
>> I still need some time to contact with the development team to check
>> whether we could get a workaround.
>>
>> I appreciate your
>> patience.
>>
>>
>> Sincerely,
>>
>> Wei Lu
>> Microsoft Online Community Support
>>
>> ==================================================
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> ==================================================
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>
From: Steven Cheng[MSFT] on
Hello David,

Thank you for the followup.

Due to some urgent issue I was absent perviously and our member Wei has
continued to help you on this issue. I was told that Wei has helped
leverage some other engineers from our product team to work with on this
issue offline. Have they helped you made any further progress or have you
informed this finding to them, I think they can help find more information
on this behavior you find.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

From: Dave on
Hi. We actually figured out what was going on. The issue lied in
setting the parameters. In pre-SP1, you could set parameters on every
postback and if they did not change, the execution did not get reset
and hence toggling works.

However, in SP1, everytime the parameters are set, the report execution
is reset. This causes toggling and sorting to fail.

The workaround was to only set parameters when they have changed. I am
still curious as to why this functionality has changed in SP1 as it was
undocumented. Is it a new feature or bug? I am currently working with
support on this.



Dave




Steven Cheng[MSFT] wrote:
> Hello David,
>
> Thank you for the followup.
>
> Due to some urgent issue I was absent perviously and our member Wei has
> continued to help you on this issue. I was told that Wei has helped
> leverage some other engineers from our product team to work with on this
> issue offline. Have they helped you made any further progress or have you
> informed this finding to them, I think they can help find more information
> on this behavior you find.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
> This posting is provided "AS IS" with no warranties, and confers no rights.

From: Wei Lu [MSFT] on
Hi Dave,

Thank you for your feedback.

Have you tried the suggestion that InvalidLastName posted?

I have provide the information to the PSS support and they will follow up
with you. Thank you!

Sincerely,

Wei Lu

Microsoft Online Community Support

From: Wei Lu [MSFT] on
Hi Dave,

Thank you for your feedback.

Have you tried the suggestion that InvalidLastName posted?

I have provide the information to the PSS support and they will follow up
with you. Thank you!

Sincerely,

Wei Lu

Microsoft Online Community Support