Visual Studio 2022, Telerik Reporting 2025 Q2, Visual Studio Designer, C# code, running VS as admin, VS version is Microsoft Visual Studio Professional 2022 (64-bit) - Current Version 17.14.13 (August 2025)

A few days ago, the data explorer window stopped functioning, while it seems to be around the same time of the last VS update, I'm not 100% sure.    The data explorer window just does not populate at all, appears to not update the screen at all (so you see whatever was there).   I have tried system restarts, repair install on Telerik Reporting, closed the data explorer window and opened it again, searched for possible answers - nothing.  I can run the report in Preview so the data connection is fine.   Attached is a screenshot of when I open the Data Explorer - as you can see while the data explorer window shows, the contents is what was there previously.  If I leave it open and restart VS the window comes up all white.   This is happening for all reports (14 in this project).

Only VS extensions installed are AWS Tookit and Telerik.

VS is not showing any errors in the output window, the option for "Show output from", at least initially, has no entries for Telerik

I am using the new Coded Reports feature in the Standalone Report Designer for .NET, and I have a class library with reports, that depends on another project.

When I try to load a report from the reports class library, I get an error that the dependent project's assembly cannot be loaded despite being present in the report folder's bin directory.

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:

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.

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".

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.

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.

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.

Graphs do not render captions and labels properly when exporting to Excel, Word, or Powerpoint. The problem appears to be worse using Skia on Linux, but the problem is present with GDI rendering as well. Worth noting that PDF export works properly. 

Here is an example report exported to Excel via a Linux Azure Web App and below that is the exact same report from the same environment as PDF:

Here is that same report as a PDF (which mirrors how it looks in the HTML5 viewer):

At the moment it's only possible to have your reports in old-fashioned projects.

It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).

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.

This bug has been reintroduced in 2025 Q3: https://feedback.telerik.com/reporting/1671864-2024-q4-pdf-rendering-made-text-extraction-impossible