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.

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.

In the latest Reporting version, the interface of the report viewer allows users to set the value of a multiselect report parameter to an empty collection but not make it null.

In some scenarios, reports rely on parameters being null to filter their data and this makes them unusable in the latest version.

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:

If we initialise the control in "FIT_PAGE_WIDTH" mode it essentially renders as expected but zooming in can actually then cause it to zoom *out*.

Reproducible in the `CSharp.NetFramework.Html5IntegrationDemo` example project as well, once you set the `scaleMode` property to "In FIT_PAGE_WIDTH".

In print preview, if you have "FIT_PAGE_WIDTH" as a default scale mode, once you click the "toggle full page/full page width" button, it's never possible to get it to return the original fit-page-width size (it seems to cycle between 3 different zoom modes, but none of them fill the entire control width).

It looks like the report viewer correctly sets the scale mode during initialization. However, when toggling the mode later, it sets it incorrectly.

I run an ASP.NET Core application that has the functionality to export reports into PDFs in an Azure environment.

There is no way to install additional fonts on Azure so I provide the fonts used in my reports via the "privateFonts" element of the Reporting configuration.

This works for the most part, the font is embedded in the produced PDFs but if I have a textbox with a large text, the text may be cut off when using the Skia engine.

I tested running my application in Docker, I copied the needed fonts in the usr/share/fonts directory of the Docker Linux container, and tried exporting again.

When exporting from Docker, with the fonts installed in the container, the text is not cut off. It seems that there is an issue when the fonts are provided as private fonts.

When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.

The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.  

I have updated to version 19.2.25.813 of Reporting, and when I try to build a project that has Reporting references, I get the following warnings:

Telerik and Kendo UI Licensing warning TKL102: Your current license has expired and is not valid for Telerik Document Processing Libraries version 2025.2.807.20.

There are no Telerik Document Processing dependencies in my project, but I still get the warning.

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

Some special characters, such as "🍁", break reports that are rendered with the Skia graphics engine in a Linux environment.

When the Gdi graphics engine is used on Linux, the reports are generated successfully. However, the Gdi graphics engine cannot be used on Linux with projects that target .NET 7 and later.

I am running the designer with the flag --roll-forward LatestMajor still getting an error in wizard when we try and open cs report

"Ensure that restore has run and that you have included 'net8.0' in the TargetFrameworks for your project."

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.

I use the kendovalidator before rendering the report to check the correct parameter of initial and final date.

However, the validation fails because additional inputs (for the "Send Email" functionality) are included in the HTML output of the viewer even though I have disabled it.

I believe that if the "Send Email" option is disabled the mail data panel should not be created.

If I try to drag & drop fields in the Standalone Report Designer for .NET, it does not allow me to paste the field, and the icon changes, indicating that the action is not allowed.

On the other hand, I can drag & drop the fields as expected when using the Standalone Report Designer for .NET Framework.