When selecting an item in the report designer (for instance a textbox) if i go in the properties and i set the anchoring property, i have to click in an other property to get my anchor property to be updated.

I have attached a video that reproduce the problem :

Select a textbox, go to anchoring in the property explorer

Set the anchoring

And click in the report itself

As you can see anchoring property hasn't been updated.

I noticed that using the Standalone Report Designer for .NET, I can't open the "ReportSource" dialog for a SubReport. The property cannot be edited from the Properties tab either.

Instead, when using the Standalone Report Designer for .NET Framework everything works fine.

When developing a Telerik report template with the intention of exporting to Excel, I observed the % sign was not displaying for positive numbers in the exported Excel file. The format we were using was {0:N2}%. The results displayed on the HTML report viewer and the Word export document was correct:

However in the excel file result, the cells were formatted without the % for positive numbers, and with the % for negative numbers.

Upon further inspection, I noticed the excel cell formatting was translated as:

This format would not generate the % symbol for a positive number as the trailing % is missing before the semi-colon.

We are fixing this by using the below Format specification directly in the Report Designer:

{0:#,##0.00"%";-#,##0.00"%"}

which is directly retained in the excel custom format:

While I understand that N, C etc. C# number formats are supported according to the design considerations and this bug is also technically resolved by using UseExtendedFormatting (setting this to false translates {0:N2} to #,##0.00"%"), this seems like an unexpected result of translating the format codes that does not match the standard behavior of {0:N2}%. Reporting this behavior for review.

When a report has a report parameter using a data source, that is visible and has AllowNull set to True, if the value initial value is invalid, no report parameter widget is loaded at all for this parameter.

If this is the only report parameter, the parameters area is not rendered at all, even though the toolbar indicates that it is active.

The issue can be reproduced by loading the attached report in the native Blazor Report Viewer.

Reports.zip

Utilizing Native Blazor Report Viewer with Telerik Blazor UI 4.0 results in some toolbar icons appearing blank. The icons are still functional.

Switching to Blazor UI 3.7 fixes the issue.

I have designed a report that includes an embedded SubReport. When I render it to PDF, it looks correct.  When I render it to CSV, there are two issues that are probably related:

1. The heading row columns should contain the main report's detail row textbox names followed by the SubReport 's detail row textbox names.  However, the SubReport 's detail textbox names are repeated a few times instead of just included once.
2. In the situation where there is no detail row in the SubReport, a CRLF is missing at the end of the main report's detail data.  The next main report detail data appears on the same row, following the previous main report's last detail column -- it should begin on the next line.

I understand that CSV Rendering is not recommend for hierarchical output as described in the CSV Design Considerations. However, I am using the Hide the SubReport if no Values to not display the SubReport when there is not data. The hidden SubReport implementation can be seen in the below binding expression.

<Bindings>
    <Binding Expression="=Count(Fields.AP_OPN_CHK_VCH_NO_C)>0" Path="Parent.Parent.Parent.Visible"/>
</Bindings>

Using the above approach, the master report is missing a CRLF when the detail data is not visible. The record shows it appended to the previous record.

I started working with Support on this issue and have discovered that it might be a bug. As a result, I am also attaching their sample to help replicate the issue. For the pdf and csv output see the first attachment in the original ticket.

The JS file with the stringResources shipped with the installation at the following location:

C:\Program Files (x86)\Progress\Telerik Reporting <Release>\Html5\ReportViewer\js

is incorrect, it should be as shown in the Localization - Telerik Reporting article.

Basically, line 9 should be changed to:

; (function (trv, $) {

while lines 178 to 180 should be like this:

    trv.sr = $.extend(trv.sr, sr);

}(window.telerikReportViewer = window.telerikReportViewer || {}, jQuery));

When HTML entities are used in an embedded expression of the HtmlTextBox, they are parsed.

The same does not happen when the "= ..." expression syntax is used.

For example:

This expression works.

= Replace(Fields.Column2, 'less than','<')

This one throws an error.

{Replace(Fields.Column2, 'less than','<')}

Here is a snippet from the file '/@progress/telerik-angular-report-viewer/dist/es/telerik-report-viewer.component.js' in Telerik Reporting NPM repository of the Angular Viewer that hard-codes the message:

TelerikReportViewerComponent.decorators = [
        { type: Component, args: [{
                    selector: 'tr-viewer',
                    template: '<div [ngStyle]="containerStyle" [attr.id]="reportViewerID" #container>Loading Report Viewer...</div>',
                    styleUrls: [],
                    encapsulation: ViewEncapsulation.None,
                },] },
    ];

Currently, there is no easy way for localizing or removing this message in an Angular-wise approach.

In this file t.folder is lowercase which should be Capital t.Folder

t.folder  throws error

 t.Folder return value

same or files vs Files

The DocumentMapVisible/ParametersAreaVisible settings that I set in the initialization of the native Blazor Report Viewer are not respected.

I can hide/show these areas from the buttons in the report viewer's toolbar but am unable to have them hidden initially.

Currently, the only workaround is to have a JS function that clicks on the toolbar after initialization:

function reportViewerMapClick() {
    $(".k-i-dictionary-add").click();
}

in the new/current Version "16.2.22.914", when dragging an DataSource-Field on the Report, the resolved expression is wrong.

In the previous Version "16.2.22.622", this worked as expected, see Screenshot.

The attached report demonstrates the issue.

I have posted a video that shows the issue.  If I use the string builder for a textbox value and select a nested property, such as DayOfWeek, for a date, then it adds:

=Fields.DayOfWeek

which fails on Preview and is wrong.  Instead it should add:

=Fields.Birthday.DayOfWeek

Please fix this.  I know that I can go type ".Birthday" to fix the issue, but it really should add the nested properties properly.

Using the Npgsql data provider of version 6.0.7 leads to the following error when there is a DateTime SQL parameter:

Can't write CLR type System.String with handler type TimestampTzHandler or Can't write CLR type System.String with handler type TimestampHandler.

This error is thrown only on Design-Time because the Design-Time value for the SQL parameter does not respect its selected DbType and is instead always a string.

I am trying to add HtmlTextBox to my report. After double-clicking on the HtmlTextBox, instead of opening the HTML editor, an error message appears 

And after that, it is not possible to delete any element of the report

When the EnableAccessibility PDF device info setting is set to true in the RuntimeSettings of a report, the text set to an item in the AccessibleDescription report item property is not respected.

For example, a PictureBox with AccessibleDescription set to "Text1" will have the "Picture Box" alternate text set in the exported PDF instead of "the Text1" string.

Recursive sub-report with hierarchical data. When expanding/collapsing, all nodes get expanded or collapsed.

I would expect only the selected node to be expanded/collapsed.

For reference, the report from the How to represent hierarchical nested data in report recursively - Telerik Reporting KB article was used as a base