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 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 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:

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.

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

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.

When the WinForms Report Viewer is initialized from within the Form.Load Event, and the RefreshReport() method of the viewer is invoked before it is added to a parent form, the following exception will be thrown: 

Telerik.ReportViewer.WinForms.Licensing.UiLicensePresenter.ShowWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.Common.TelerikLicensePresenterBase.PresentWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.WinForms.WinViewer.OnPaint(PaintEventArgs eventArgs)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lpa

I have been forcing my webservice data source into a workable solution for making GraphQL requests. Right now in order for us to use GraphQL, we have to build out the request manually with a string such as the following:

{"query: "query GetSomeResult($input: Int!) {result {id name}}",
"variables": "{"input": @parameter}"
}

While this is a normal way to hand craft a GraphQL request, the issue I have is that it shouldn't need to be that hard. Also I get no intellisense or suggestion in regards to the data returning. This means that when I try to bind data to a text box, I have to visually validate that the [=Fields....] is actually correct by looking at the GraphQL query and at the code base. I would love to see the ability to to just say have a set of standard api technologies we could implement from such as GraphQL queries, GRPc queries, or any other contract style request. I would expect that the data source logic would be smart enough to parse the query (at least for GQL) and be able to provide reccomendations.

Also a major issue we have had is in being able to pass that data source to subReports, or dealing with any nested objects such as a user.address.addressLine1 would not be able to be found if address is a nested values like the following

user: {
  address: {
    addressLine1
  }
}

I set globally the culture on the Linux Ubuntu Docker Container. Interestingly, the negative currency with en-US and fr-CA was displayed with the '-' sign rather than in brackets.

This was reproduced even in the values set with the Text Function FormatWithCulture(cultureName, format, args). The function displayed wrong formatting also on Windows, even in the Standalone Report Designer for .NET 8.

When the global culture on Windows was en-US, the negative decimal value formatted without the FormatWithCulture function was displayed correctly in .NET 8.

In the .NET Framework, the negative currencies were displayed as expected in all scenarios.

I have linked also a muted video showing the issue.

Telerik.Reporting.nupkg has a dependency on ResXResourceReader.NetStandard.

Our 3rd party security audit has found the missing Digital Signature of this DLL. A digital signature would aid in verifying its authenticity and integrity.

we need to have complete End User Tutorial for Web Report Designer, where all the excel like features need to be demonstrated.

including Pivot etc.

The Web Report Designer does not entirely comply with CSP standards, necessitating the use of the 'unsafe-eval' directive in our CSP policies to enable its functionality.

This directive poses significant security risks and undermines the purpose of implementing CSP in the first place. Please remove this requirement.

If I use an HTML5-based Report Viewer with the default CONTINUOUS_SCROLL page mode and I start scrolling to the next page, the Get Document Page request is made multiple times for the same page.

If I move to the next page via the toolbar buttons or if I use the SINGLE_PAGE page mode, then problem is not reproduced.