Declined
Last Updated: 23 Jul 2025 15:36 by ADMIN
Thomas
Created on: 10 Jul 2025 13:46
Type: Feature Request
1
Add a new property ex "DisableParameterArea" for the ReportViewer that disables and does not render to the ParametersArea

Greetings,

Telerik.Reporting version: 19.1.25.521

ASP.NET Web Forms

Our team recently had a some trouble understanding the behavior of the ReportViewer.ParametersArea and the property "ParametersAreaVisible". Our desire was to hide this to the end user because the ParametersArea should not be fiddled with directly by the our end users; sensitive data could be accessed. Setting this to false does not stop the render of the ParametersArea. Typically setting the property on a control in ASP.NET Web Forms means the control will not render to the page. So having a property named "ParametersAreaVisible" is misleading in my opinion. I know the ParametersArea is thought as a benefit to the end user but in our case we do not desire this.

My feature request is to add a new property "DisableParameterArea" to the ReportViewer that causes the ParametersArea to not render to the ReportViewer.

 

Thank you

3 comments
ADMIN
Ivan Hristov
Posted on: 23 Jul 2025 15:36

Hello Thomas,

My name is Ivan Hristov and I'm the engineering manager of Reporting team.

I understand your frustration, and I agree that the current behavior of the parametersAreaVisible option can be unintuitive and potentially misleading. We'll update our documentation, providing better explanation how this property is intended to work.

Regarding your suggestion for a dedicated property that explicitly disables the PA: this hasn't been considered so far as the same effect can be achieved through the report parameters visibility, as suggested by Dimitar. However, we'll monitor the votes in the feedback portal item, and if more users need such property, we'll definitely discuss its implementation.

While on the Report Parameters' Visible property: I can imagine in some scenarios one might want to control the parameters visibility based on the currently logged-in user - and that is something we will discuss with the development team. In case your scenario is different, please share it so we can consider this case in our discussion.

I hope this helps clarify things and reassures you that we take user feedback seriously. I'll open a support ticket on your behalf to continue the discussion without cluttering this thread. If you’re open to it, we’d also appreciate any additional insights into the issues you’ve encountered with Telerik Reporting recently.

Thank you in advance for your understanding.

Regards,
Ivan Hristov
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Thomas
Posted on: 17 Jul 2025 13:26
That's fine, its your software, your lengthy explanation proves a point. How are developers supposed to know that setting the Report Parameters to Visible will have the desired effect? Oh thats right, probably buried in some remote documentation article that were supposed to just know. I stand by my suggestion. I will be recommending we stop using Telerik.Reporting as it has caused as far too much drama in the fast few months, from updates that change the report to not function correctly, to adding unintended functionality, to just having to add license proof to remove watermarks.Thank you.
ADMIN
Dimitar
Posted on: 17 Jul 2025 13:15

Hi Thomas,

Thank you for the feedback!

I assume that you are referring to the HTML5 WebForms Report Viewer and not the legacy ASP.NET WebForms Report Viewer, considering that you are using the latest version(where the legacy viewer is not available as it was retired).

Indeed, when you hide the parameters area through the "ParametersAreaVisible", the area won't be visible on the page, but the element with class .trv-parameters-area is still loaded in the DOM with the available parameter values.

This is because it is intended that this setting is used only to determine whether the parameters area will be visible by default, but still allowing end-users to hide/show it by clicking the toggle button in the toolbar.

When you do not want the parameters with their available values to be written in the DOM, you must set the Visible property of the report parameter to False. That way, this parameter won't be loaded in the DOM. You can do this for all report parameters that contain sensitive data, or for all of the report parameters in the report -Report Parameters at a Glance - Telerik Reporting.

The report viewer will still generate a .trv-parameters-area element in the DOM, but now that the parameters are hidden on the server, their values won't be inserted in the DOM, and the wrapper will be empty:

This is the recommended way to go when needing to hide the report parameters and their values from the page. Adding an additional property would do the same as hiding the report parameters from the report definition settings, and since that option is already available - we have decided to decline this feature request.

I hope that the suggested solution will work for your needs. Please let me know if I can assist with anything else.

Regards,
Dimitar
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.