Report viewer losing parameters when clicking 'back'

[Mr_4el]

Scenario:

I have 2 reports:

Report A, a simple list containing a parameter for a filter. Contains a row-level reference (action: Go to report) to another report B, which passes the parameter for the filter.

When opening report A (iow RSViewerPage.aspx), a parameter is requested. I enter it and click "Apply". The report is loading correctly. The Parameters panel displays the name and value of the report parameter A.

Now I click on the link to go to report B with the specified parameter. The report opens correctly and displays the correct name and value of the parameter for Report B.

So far, everything has been fine.

Now I click the "Back" button in the report viewer (in the browser), and it takes me back to Report A with the original (standard) filter enabled (the previously selected filters should be indicated). The problem is that there are still default settings in the Options panel. In addition, when switching back, the page takes a while to load. Previously, in the SSRS 2008 version, switching back was performed instantly.

[Mr_4el]

This solution is not suitable. 

Currently, when switching back in the browser, the contents of the report are displayed taking into account the previously selected parameters (the report script is not executed in this case), and the page is being re-rendered. The parameters become the default. And in the page properties, in the "Response Headers", the "Cache-Control" property has the value "no-cache".,

[v-bmanikante]

Hi @Mr_4el ,

Thank you for the followup. In modern SSRS versions, when using the browser Back button, the report content may appear correct due to browser caching, but the parameter panel resets to default values.

This is caused by the CacheControl: no-cache header, which prevents SSRS from retaining the previous parameter state.

This behaviour is by design and differs from SSRS 2008, which cached both the report content and parameters.

We can try, a custom "Back" action in Report B that navigates to Report A with the original parameters or use URL parameters or session storage (if using a wrapper app) to retain parameter values.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Regards,

B Manikanteswara Reddy

[v-bmanikante]

Hi @Mr_4el ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Please don't forget to give a "Kudos " – I’d truly appreciate it!

Regards,

B Manikanteswara Reddy

[v-bmanikante]

Hi @Mr_4el ,

Thank you for reaching out to Microsoft Fabric Community Forum.

As we haven’t heard back from you, we will go ahead and close this ticket for now.

If you need any further assistance, please don’t hesitate to raise a new ticket, we’re always happy to help.

Our sincere apologies if there was any inconvenience caused.

Regads,

B Manikanteswara Reddy

[v-bmanikante]

Hi @Mr_4el ,

Thank you for reaching out to Microsoft Fabric Community Forum.

@Poojara_D12 Thank you for quick response.

@Mr_4el we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.

If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Please don't forget to give a "Kudos " – I’d truly appreciate it!

Regards,

B Manikanteswara Reddy

[Poojara_D12]

Hi @Mr_4el 

In newer SSRS versions (after 2008), when you use the browser's Back button after navigating to another report, the original report reloads with default parameters instead of keeping the previous ones. This happens because modern SSRS doesn't cache report state like SSRS 2008 did. To fix this, use a custom "Go to Report A" action in Report B and pass the parameters explicitly—avoid using the browser back button.

[Mr_4el]

This solution is not suitable. 

Currently, when switching back in the browser, the contents of the report are displayed taking into account the previously selected parameters (the report script is not executed in this case), and the page is being re-rendered. The parameters become the default. And in the page properties, in the "Response Headers", the "Cache-Control" property has the value "no-cache".