Design time error while changing the report property

[Yoly]

Hi,

when you try to change the Report while having the visibility property set to false it will give you the following message:

 “Property value is not valid.
Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the <configuration>\<system.web>\<httpModules> section in the application configuration.”

At the moment you can only change the report property in design time when the visible property is set to true.

I’m using the Q3 2008 version of Telerik Reporting.

Regards,
YCeron

[Steve]

Hello yceron,

We have not been able to reproduce the error on our end. Here is the code we've tried:

 protected void Button1_Click(object sender, EventArgs e)
        {
            ReportViewer1.Visible = !ReportViewer1.Visible;
        }

        protected void Button2_Click(object sender, EventArgs e)
        {
            ReportViewer1.Report = new Report3();
        }

Tried it with both Inproc and Outproc session. Please elaborate on your exact scenario causing the error.

Regards,
Steve
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

[Yoly]

Actually, this only happens in the Design time editor. In run time it works ok, I just wanted to point out the bug, so it might be fixed in future releases.

An easy way to reproduce this error is to open one of the sample solutions:
1. Open ReportExamples.sln from the Telerik Reporting demos (vb.net or C#).
2. Open the ReportViewer.aspx in design time.
3. Select the Reportviewer1 and change the visible property to False.
4. Try to change the Report property to one of the reports that are available for example the BarcodesReport and you'll get the Property value is not valid error message.

If you change the visible property back to True it lets you change the report property without any problems.

[Steve]

Hello yceron,

Thank you for the clarification and sorry for the initial misunderstanding. We were able to reproduce the problem with the steps you have provided and logged the problem in our bug tracking system for further investigation and fixing.

We've also updated your Telerik points as a token of gratitude for bringing this to our attention. Do let us know if other questions/issues surface.

Sincerely yours,
Steve
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.