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

We'd like to have a settable property on the web designer and report viewer which takes a function which returns an access token.
This way a new access token can be requested by the designer/viewer when the current one expires.

This is usually used in the following way:

1. Implement a function with signature "string GetAccessToken()"
2. Set that function to the property AccessTokenProvider of the designer/viewer
3. Designer/Viewer wants to make a request and fetches and caches the access token
4. Designer/Viewer uses that access token until it hits a 401 upon which
   1. The Cached access token is cleared
   2. A new Access token is fetched from AccessTokenProvider and then cached
   3. Retry the request with the new access token
   4. Should the retry also fail return the failure

Should the above be to specific/inflexible:
Instead of caching the access token, call AccessTokenProvider for every fetch but also provide an additional parameter with the "reason" for the call, so the implementer of AccessTokenProvider can decide themselves when to return a cached AccessToken or generate a new one.

Actually Axis title can move only on his specific axis.

For example, x-axis title can move left to right and y-axis title can move up to down.

But in same cases, like mine, where the axis are not on the edge of the chart (because it involves negative x and y values and the intersection is in the middle of the field) it is necessary to move the x-axis title up and down to be next to the x-axis position, or to move y-axis left/right to be next to the y-axis position.

Feature request: allow axis titles to be moved on both axis and not only one.

In attach you'll find a screen that shows the desired result.

Best regards

Hi Support team,

On ServerSide, when using a CultureInfo, with a NumberSeperator different then '.', e.g. CultrerInfo("de-DE"), it is not possible to Save a report.

It seems it is internally converted to a string based value and gets the different seperator and than can not be casted/converted back to double.

Best regards

Alexander Schneider

System Development | Loy & Hutz Solutions GmbH

If I set both the "EnableAccessibility" and "ViewerRenderToolTips" device info settings to true, the generated PDF document is corrupted.

Hi Team,

I have a request for being able to add the `User-Agent` header to reporting calls. We've ran into some image hosting sites that will not resolve image links properly if the user-agent is not present in the request and returns a 403 Forbidden error. Any browser that passes the user-agent parameter can resolve this link.

https://cms5.revize.com/revize/cityofwillmar/_assets_/images/logo.png

But telerik will return this error:

Telerik.ReportDesigner.exe Error: 0 : An exception has occurred while processing 'pictureBox1' item:
System.Net.WebException: The remote server returned an error: (403) Forbidden.
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   at System.Net.WebClient.DownloadData(Uri address)
   at Telerik.Reporting.Processing.Imaging.ImageUtils.LoadData(String filePath)
   at Telerik.Reporting.Processing.Imaging.UrlImageItem.CreateUnderlyingImageItem()
   at Telerik.Reporting.Processing.Imaging.UrlImageItem.get_UnderlyingImageItem()
   at Telerik.Reporting.Processing.Imaging.UrlImageItem.CreateImageInfo()
   at Telerik.Reporting.Processing.Imaging.IImageInfoMapExtensions.StoreImageData(IImageInfoMap imageInfoMap, IImageItem imageItem, ICache cache)
   at Telerik.Reporting.Processing.PictureBox.ResolveImage(Object value)
   at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)

Currently, the only way around this is to fetch the images with a custom user function and returns the images to the Reporting Engine as a byte array or other supported format. It's a lot of overhead for something that could simply be toggled on an off, so I think this would be a nice feature addition. 

Thanks,
J.T.

Hi Telerik Team,

We are experiencing an issue related to tooltips in PDF exports from Telerik Reporting.
When we enable tooltips using the ViewerRenderToolTips setting both at the report level and through the device info in the report service, tooltips are appearing in the exported PDF—but they are being rendered as text annotations, not as normal tooltips.

Issue:
In the resulting PDF, tooltips are rendered as Text Annotations, which:

1.Appear as popups or sticky notes on mouse hover/click
2.Are not the standard tooltip experience expected by users
3.May affect accessibility compliance and user readability

Expected Behavior:
Tooltips should appear as standard PDF tooltips (like browser-style hover text) instead of annotations.

We use WPF Report Viewer in our application. For testing, validation, and automation purposes, we need to:

• Uniquely identify each element in the XAML rendered report contents to support automation.
• Prevent the element ID changes. The generated item IDs must remain consistent as long as the report definition is not changed.

While customising templates/CSS, I noticed the .trv-parameters-wrapper div as follows:

<div tabindex="300" class="trv-parameters-wrapper" aria-label="Parameters area. Contains 4 parameters.">
<div class="trv-parameter-container k-card"></div>
</div>

Currently, the VS item templates, and the documentation suggest using app.UseEndpoints for route registration in ASP.NET Core.

It would be better to use top-level route registrations like app.MapControllers() and app.MapControllerRoute() directly.

When using the "Close"/"Close All" options when a report has unsaved modifcations, a warning is shown, but you are forced to save the report or close the window/tab to leave definition file unmodified.

A "close and discard changes" option is helpful and convenient - one can cancel some edits without hoping that a bunch of "Ctrl - Z" presses will clear everything, refer to one report without concern about accidental modifcations (can be editing others), etc.

I use the font Roboto in a TextBox rotated vertically. The last character of the content is cut in the design time of the Standalone Report Designer. In Preview and when exporting to PDF, the content is displayed as expected.

Here is a link to a video showing the issue - https://somup.com/cTQjid8GRH

I try to select the Series Group for my LineSeries directly from the Graph Properties pane in the Standalone Report Designer, but the groups are not listed in the dropdown:

I am able to do this from the GraphSeries Collection Editor, though:

I’m using Telerik.Reporting v19.1.25.521 to generate PDF files. After upgrading the Telerik.Licensing NuGet package to version 1.6.16, all SVG files stopped rendering in the output.

Reverting back to the previous version resolves the issue. I also tested the latest available version (1.6.21), but the problem still persists.

I am currently working on adapting our documents to meet EAA accessibility requirements, and I have upgraded Telerik Reporting to version 19.2.25.813.

I added { "EnableAccessibility", true } to the device information settings when exporting to PDF.

However, when I run the generated PDF through the PAC accessibility checker, it reports the following error:

One or more checks could not be completed.

Please copy the error message and send it by email to pac@axes4.com so that we can improve the product.

PAC (24.4.2.0)

Stacktrace 1:
Not Same Dimension.

   at LiM40lTFOn0eWLuaajvf.A1qp40TFKIn2jBWwxv0d..ctor(Byte[]  , Byte[]  )
   at UmAt0CTVmfKfDqmcrmt6.HLJIPdTVqEyuiUM22OWj.eILTFMl6QDL(Byte[]  , Byte[]  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.ss4TFEoiqAI(geZKyFTFS41IUbuH7c4u  , WdRarplBO5RB6PweG24O&  , HLJIPdTVqEyuiUM22OWj  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.NkpTFX7G98N(Stream  )
   at G3eiSBGKQYDyZb8MKn4.s1GbJnGU5fGAYJDEswn.YUrlmAmFmey(InR8VoTVQP2XaLkCJpHB[]  , String&  )
   at vjQ4yllNOb51ltZ35aif.BbwuGqlNKtxwJLI1h3YW.OnText(RkwmSj3AKXUF7SYMBus  )
   at zSuFuLlooBaWZ1KqkqIR.Xjv9w4loJqr1RoZtRHCI.OHEloDJOVda(Action`1  )
<===========================>

Stacktrace 2:
Not Same Dimension.

   at LiM40lTFOn0eWLuaajvf.A1qp40TFKIn2jBWwxv0d..ctor(Byte[]  , Byte[]  )
   at UmAt0CTVmfKfDqmcrmt6.HLJIPdTVqEyuiUM22OWj.eILTFMl6QDL(Byte[]  , Byte[]  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.ss4TFEoiqAI(geZKyFTFS41IUbuH7c4u  , WdRarplBO5RB6PweG24O&  , HLJIPdTVqEyuiUM22OWj  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.NkpTFX7G98N(Stream  )
   at G3eiSBGKQYDyZb8MKn4.s1GbJnGU5fGAYJDEswn.YUrlmAmFmey(InR8VoTVQP2XaLkCJpHB[]  , String&  )
   at vjQ4yllNOb51ltZ35aif.BbwuGqlNKtxwJLI1h3YW.OnText(RkwmSj3AKXUF7SYMBus  )
   at zSuFuLlooBaWZ1KqkqIR.Xjv9w4loJqr1RoZtRHCI.OHEloDJOVda(Action`1  )
<===========================>

Stacktrace 3:
Not Same Dimension.

   at LiM40lTFOn0eWLuaajvf.A1qp40TFKIn2jBWwxv0d..ctor(Byte[]  , Byte[]  )
   at UmAt0CTVmfKfDqmcrmt6.HLJIPdTVqEyuiUM22OWj.eILTFMl6QDL(Byte[]  , Byte[]  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.ss4TFEoiqAI(geZKyFTFS41IUbuH7c4u  , WdRarplBO5RB6PweG24O&  , HLJIPdTVqEyuiUM22OWj  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.NkpTFX7G98N(Stream  )
   at G3eiSBGKQYDyZb8MKn4.s1GbJnGU5fGAYJDEswn.YUrlmAmFmey(InR8VoTVQP2XaLkCJpHB[]  , String&  )
   at tyAsEn3twQpti0lgIPO.RkwmSj3AKXUF7SYMBus.get_UnicodeText()
   at Xw4lWvlCL4434RXaMsKT.F5WZJylCrhBUjVHuUbsX.OnText(RkwmSj3AKXUF7SYMBus  )
   at zSuFuLlooBaWZ1KqkqIR.Xjv9w4loJqr1RoZtRHCI.OHEloDJOVda(Action`1  )
<===========================>

Stacktrace 4:
Not Same Dimension.

   at LiM40lTFOn0eWLuaajvf.A1qp40TFKIn2jBWwxv0d..ctor(Byte[]  , Byte[]  )
   at UmAt0CTVmfKfDqmcrmt6.HLJIPdTVqEyuiUM22OWj.eILTFMl6QDL(Byte[]  , Byte[]  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.ss4TFEoiqAI(geZKyFTFS41IUbuH7c4u  , WdRarplBO5RB6PweG24O&  , HLJIPdTVqEyuiUM22OWj  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.NkpTFX7G98N(Stream  )
   at G3eiSBGKQYDyZb8MKn4.s1GbJnGU5fGAYJDEswn.YUrlmAmFmey(InR8VoTVQP2XaLkCJpHB[]  , String&  )
   at tyAsEn3twQpti0lgIPO.RkwmSj3AKXUF7SYMBus.get_UnicodeText()
   at ysJjM9lSiQESKK4PGybl.Ew1sjolSWTTCG8Dr2kJW.w3BlSPYBDdu(Os7IcEbiPhfT5JvSVNB  )
   at System.Linq.Enumerable.All[TSource](IEnumerable`1 source, Func`2 predicate)
   at System.Linq.Enumerable.All[TSource](IEnumerable`1 source, Func`2 predicate)
   at System.Linq.Enumerable.All[TSource](IEnumerable`1 source, Func`2 predicate)
   at k8l6oaleGgjW6MRKlmWI.IHPaBIlekNuIBbsppXFp.OnStructureElementStart(G23gGNHErJQY3Wrw4QJ  )
   at zSuFuLlooBaWZ1KqkqIR.Xjv9w4loJqr1RoZtRHCI.OHEloDJOVda(Action`1  )
<===========================>

Stacktrace 5:
Not Same Dimension.

   at LiM40lTFOn0eWLuaajvf.A1qp40TFKIn2jBWwxv0d..ctor(Byte[]  , Byte[]  )
   at UmAt0CTVmfKfDqmcrmt6.HLJIPdTVqEyuiUM22OWj.eILTFMl6QDL(Byte[]  , Byte[]  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.ss4TFEoiqAI(geZKyFTFS41IUbuH7c4u  , WdRarplBO5RB6PweG24O&  , HLJIPdTVqEyuiUM22OWj  )
   at Qww7PoTFksraZMkU6m8a.sxUvkLTF4dybUR9VwcRe.NkpTFX7G98N(Stream  )
   at G3eiSBGKQYDyZb8MKn4.s1GbJnGU5fGAYJDEswn.YUrlmAmFmey(InR8VoTVQP2XaLkCJpHB[]  , String&  )
   at tyAsEn3twQpti0lgIPO.RkwmSj3AKXUF7SYMBus.get_UnicodeText()
   at bKc5VfoKOVpfI2iB89a.DBfa8VoUYxTZI0B53G7.get_UnicodeText()
   at q7u9wileh20pIa0tWKql.tdng87le0gdU2UFgOyxR.OnMarkedContentStart(Yeb5V1SeYY62eYUqquq  )
   at zSuFuLlooBaWZ1KqkqIR.Xjv9w4loJqr1RoZtRHCI.OHEloDJOVda(Action`1  )

The problem doesn't occur if I upgrade to an older Reporting version.

When importing a report with the Standalone Report Designer for .NET, if the report or its items use report events, they are not automatically imported into the TRDP file.

It is currently necessary to manually type the method names in the corresponding properties in the report designer.