I am using the HTML5 Report Viewer and have a multi-page report. When the report is previewed with the default pageMode setting, where pages are continuously scrollen into, the found search results are correctly highlighted.

However, if I use pageMode="SINGLE_PAGE" in the HTML5 Report Viewer initialization code, and I navigate to page 2 or further, the found results are not highlighted.

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

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.

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.

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

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.

In the standalone designer, it would be helpful if you could drag and drop the column headers to reorder.  At present you have to add a new column and delete the old one, remembering to copy all properties.

Is there a way to have the linear gauge display a value above the indicator?

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.