I have a .NET Framework 4.7.2 ASP.NET MVC project.

I am currently on Telerik.Reporting 19.0.25.211. I also have Telerik.Licensing package 1.4.10 installed on the project.

After upgrading my project to Telerik.Reporting 19.0.25.313, without touching the licensing package, in my .csproj file I'm seeing Telerik.Licensing.Runtime reference is set to 1.4.6.0, although the nuget package manager says that I have 1.4.10 installed.

In the project References also appeared a reference to the old Telerik.Licensing version after the update.

I am using the Blazor wrapper of the web report designer.

When i first time after running my blazor app visit page with WebReportDesigner everything works as intended:

but when i exit and revisit it later this is a result:

Is it possible to get descriptive information exposed for the ReportsControllerBase swagger endpoints? do they exist?

Notice how the About and files endpoints have information next to them:

Like-wise how the files endpoint has descriptive parameters:

In the Report Preview of the Web Report Designer, there does not seem to be a way to provide a null value to a nullable data source parameter.

For example, I have a nullable DateTime parameter. After the data source is configured the data source parameter DataType is set to String, it did not resolve to nullable DateTime. Even after I change the data source parameter to DataType of DateTime it cannot accept a null value from a DateTime report parameter, it seems to be interpreted as a string instead of null.

In the Standalone Report Designer there is no problem having a DateTime report parameter passing null to a nullable DateTime data source parameter; after reconfiguring the data source in the Standalone Report Designer the DataType for the data source parameter is <DataType>System.Nullable`1[System.DateTime]</DataType> instead of <DataType>System.DateTime</DataType> as from the Web Report Designer.

The Telerik Reporting REST Service storage is automatically cleaned based on some configurable timeouts and hardcoded times. It requires an awaken service to be performed.

It would be very useful for the developer to be able to invoke manually the storage cleaning functionality either with code or through the service Web API.

Currently, when using External Stylesheets in the reports, the engine tries to first load the stylesheet as an embedded resource of the assembly. If it fails to load it from the assembly, a message is written to the trace along the lines of:

ESS: Attempt to load ExternalStyleSheet from EmbeddedResource from assembly Telerik.Reporting, Version=19.0.25.211 with resource name styles.xml is unsuccessful.

After this, the engine will try other ways to resolve the stylesheet such as from URI and if it succeeds, the report will render as expected.

This can create confusion because looking at the trace, one might think that there were errors with the rendering of the report because the stylesheet did not load but it was actually successfully loaded with one of the other approaches.

It would be better to write the errors to the trace only if the stylesheet does not load after all attempts.

The PDF with enabled Accessibility looks fine in the Adobe PDF reader.

However, when I check it with the PAC tool, it shows in the logical structure the Detail section first, then the Page Header, and then the Page Footer.

In the Web Report Designer's objectDataSource wizard, once the "Preview data source results" (step 4) are ready and the Finish button is clicked, there is another call to the data source member but instead of using the Design-Time Values for the member, the values in the Value column appear to be used.

For example, If report parameters are already assigned to the data source parameters the string of the Value (e.g. "= Parameters.StartDate.Value") is used instead of the actual report parameter value.  I think the data member call to generate the data schema should be the Design-Time Values again. In order to get the data schema generated I had to use the same values for Value column as in the Design-Time Values value.

After the data source parameters are assigned to report parameters then it breaks the generation of the data schema later when the report is opened again in the Web Report Designer and there is an error (e.g. Error An error occurred while loading the data schema for "Widgets". ("Message"."String was not recognized as a valid DateTime.").

 I cannot create a Report Parameter with the same name as a data source parameter or CSV data source field. Trying to do so results in an error messagе

(Error Could not change property 'Name'. Name 'FromEffectiveDate' already exists).

This issue can be demonstrated in the Web Report Designer Demo page: create a parameter for the yearDataSource data source, try to create a report parameter with the same name to get the error.

Using report parameter names that are also data source parameter names works fine in the Standalone Report Designer.

Hello,

the search results in a PDF generated with report is not correct. Again...

Please fix this bug and add this scenario to your tests.

Steps: Search for a text in a pdf.

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

Hi,

In Desktop Designer, I create a very simple Report with :

• a JSON datasource mapped to the report
• a Table with two colunms

I want to duplicate this table, so I select it and do a copy. After that, I select the detailSection and do a paste. The pasted table, in the Report Explorer look fine, but in the designer view it is not the case. And if I compare the TRDX files, an entire section is missing (the <Cells> section).

Attached files :

• Multi-zone.trdx : Before copy/paste
• Multi-zone-2.trdx : After copy/paste
• Screenshot.png : screenshot of the Designer where you can see the two tables and the Report Explorer

Thank you

PS: In additional informations, I specify ASP.NET MVC as Project Type, but it is not relevant.

I have the chance to use a 27", 5120 x 2880 monitor, with text on Windows set to 200%.

The problem with Telerik Report Designer is that the icons in the report designer are very small and barely usable:

- Panel icon to move it.
- Table icon to move it.
- The open / close icons in the Report Explorer.

Also the zoom indicator at the bottom left of the screen, where the text part is too small to display the current zoom.

The HTML5 Report Viewer uses inline templates which may require enabling the unsafe-eval CSP policy.

The viewer should migrate to using CSP templates as shown in Getting Started with Content Security Policy (CSP) Templates - Kendo UI Templates - Kendo UI for jQuery.

When using a date parameter with AutoRefresh set to True in the Standalone Report Designer, selecting a new value from the date picker does not automatically refresh the report viewer to show the updated report. To make the new value take effect, you need to move the focus away from the date picker.