Refresh/Cache issue with telerik reporting

[Sundar]

Hello,

I handle user inputs thru combo box and construct SQL based on the combo box selected values and create dataset and assign it to the report.

When I call the reports first time, it shows the values correctly.

When changed the values of combobox, it displays the report for previously seleted value of the combobox. This behavior is quite consistent.

I check few values during the page load event and based on that i call a function to generate SQL and call report using new report().

Is it a caching issue? How can this be solved?

Thanks
Sundar

[Steve]

Hello Sundar,

Please review the following video for more info: Telerik Reporting - Design Time Support for Parameterized Queries.

Kind regards,
Steve
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Sundar]

Hi,

Based on my investigation, the issue looks more like a cache problem.

Actually, from the comboboxes, whenever i am changing to new values and querying to get a report, it is constructing new SQL and the dataset is also generated, but while displaying it displays previously generated report.

But everytime, before I request for a new report, if i clear my cache, then I see the correct report.

Thanks
Sundar

[Steve]

Hi Sundar,

This sounds like a bug we had in a previous version of the product. Please upgrade to the latest version Q1 SP1 and let us know if still having problems. If you cannot upgrade, you can use the workaround by setting EnableViewState="false" to the report viewer.

Greetings,
Steve
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Sundar]

We are using the Q3 2008 version. We have also tried the 'rptControl1.EnableViewState = "False"' method and it does not seem to help anyway. Is there any other workaround other than upgrading to the new version? Please assist.

[Sundar]

Hi,

Awaiting your support here, your reply is highly appreciated.

[Steve]

Hi Sundar,

I've been unable to replicate such a problem. Find attached a sample project that works as expected - review it and let us know how it goes.

Sincerely yours,
Steve
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Mahdy]

I found a dirty solution. Before load a report in report viewer I removed some keys from cache. I used following code and it worked for me.

        protected void RemoveKeyFromCache(string key)
        {
            foreach (System.Collections.DictionaryEntry entry in HttpRuntime.Cache)
                if (entry.Key.ToString().IndexOf(key) >= 0)
                    HttpRuntime.Cache.Remove(entry.Key.ToString());
        }

        protected void ClearCache()
        {
            for (int i = 0; i < Session.Count; i++)
                RemoveKeyFromCache(Session.Keys[i].ToString());
        }

        protected void LoadReport()
        {
            ClearCache();

            //load report code here 

            ReportViewer.RefreshReport();
            ReportViewer.RefreshData();
        }

[Hanna]

I have pretty the same issue. My report is showing balances. And balances could be changed any time. So if i run report first time - it shows actual balances (2 lines in report). If then i'll change balances and run report second time - i see cached result (2 lines instead of 3, even if i see in debug mode that my sql query returns 3 records and send them to show into report).

I am using ReportViewer, latest version of Telerik reporting. I am using FileCache. 

Any ideas how to fix it? I've tried to clear cache and session as suggested above - didn't help

[Nasko]

Hello Hanna,

This forum thread is about the legacy ASP.NET Web Forms Report Viewer.

Your scenario does not use the legacy viewer, so we replied directly in your support ticket with more information on how to solve the issue with the HTML5 Report Viewer and REST Service:

"We introduced a way to modify the default cache behavior with the latest internal build of Telerik Reporting.
The default cache expiration time is 30 minutes and the time may be extended if the cached report instance is in use. If the cache instance is not used for 30 minutes, a consecutive request to the Reporting REST service clears the cached report."

Regards,
Nasko
Telerik

 

 

[Amit]

The report is not refreshing due to compatibility issue in IE 11 and chrome. Currently, we have a workaround, we click the compatibility checkbox in IE and ask the user to work but it is not possible to  every user so we have to fix it in code.

[Amit]

The Telerik report is not refreshing due to compatibility issue in IE 11 and chrome. Currently, we have a workaround, we click the compatibility checkbox in IE and ask the user to work but it is not possible to explain to every user so we have to fix it in code. Please find the attached screenshot.

Appreciate your help and support in advance.

[Stef]

Hello Amit,

The recommended troubleshooting approach for the HTML5 Viewer is to use Fiddler or other proxy tool to check the requests, their responses and statuses. With Fiddler, information about requests and responses content can be seen in Fiddler - Inspectors - Request/Response - Raw tabs.

Please open a support ticket including the markup of the page with the viewer and details about the used Telerik Reporting version.


We will need also a SAZ file generated by Fiddler to trace the requests and their responses' content.

Regards,
Stef
Telerik by Progress

[Amit]

We are using 2013 Q3 License version of Telerik.

[Stef]

Hello Amit,

We will need to investigate the problem further. Please open a support ticket and send us:

• SAZ file generated by Fiddler
• The markup of the page with the viewer
• The implementation of the Reporting REST service

On a side note, our recommendation is to upgrade the project to use the latest R3 2016 SP1 version of Telerik Reporting, as Q3 2013 is the first version in which we introduced the HTML5 Viewer. There are changes related to the HTML5 Viewer, Reporting REST service and their functionality through years.

Regards,
Stef
Telerik by Progress