I have a JsonDataSource that contains a Base64 string field I want to use in a PictureBox.

When I drag the field from the Data Explorer in the Report Designer, it creates a TextBox with the text content. When I run the report, there is an error "A generic error occurred in GDI+'.

Consider creating PictureBox when dragging a Base64 string instead of TextBox.

There is a common error message received often after upgrading Telerik Reporting:

Unable to get report parameters. An error has occurred. Cannot read a document with the specified schema: http://schemas.telerik.com/reporting/2023/1.1. You might be using an older version of the product.

Obviously, I have a mismatch between the new report that I created and the deployed Reporting application. To create the report that is generating this error, I copied from an existing (and working) report.  Only changed the Stored Proc being called and a few field names.  Everything else is the same.

Except -- (OBVIOUSLY) -- when I saved the report -- the Designer changed the schema version. 

You need a way in the DESIGNER to display the schema version of the report. If these reports are TRDP then I don't see an obvious way of viewing the schema version of the report. I opened both reports in the designer and tried to find a way to view the schema versions of a working versus non-working report.  So that, I could determine which version of the designer that I need to drop back to (in order to create my copy of an existing report).

In your error message, you could easily provide additional detail but do not. You just say "product". Obviously, you know this but you don't report it to user.  For example, you could say -- "This report has schema version xx.xxx.xx but the Reporting Engine can only run reports of schema version yy.yyy.yy and below" or something to that affect.  Good error messages would go a long way to avoiding this frustration.

The following error is thrown during design time when a Barcode has a static value but one or more of its properties are bound to a report parameter through Bindings.

When actually previewing the report, the Barcode works as expected.

I need to know when one of my users has canceled the rendering of the report in order to update the UI accordingly.

Please consider firing a 'renderingCanceled' event when the above occurs or passing an additional parameter to the updateUi event to specify the rendering state.

If the CanGrow property of a TextBox/HtmlTextBox is set to True and Left and Right Anchoring is applied, the Height of the text box will be determined based on its design-time Width.

Thus, even if the actual final Width of the item is enough to fit its contents on a single row, the text box can have a larger than necessary Height.

When rendering a report with a Graph on Linux, the labels of the Graph are not aligned properly.

For example, right-aligned labels are offset to the left depending on the content and length of each label.

I apply the operator TOP N (=5) to get only the first 5 records of a dataset sorted by a DateTime field. It sorts the data correctly as seen in the previewed report, but still returns all data records rather than the first 5 of them.

If I apply the TOP % operator, the dataset seems filtered as expected.

The workaround I have found is to apply second TOP N filtering with an empty expression as seen in the linked screenshot.

I have attached also a sample report demonstrating the issue and the workaround.

This is not a clone. It's a new request I had to add, since the old was closed with a technically fault answer. By technically fault I mean possible, but in real scenario unusuable.

F.e Jasper's SubReports have a property called DataSource. The sub-reporst uses this dataSOurce for rendering it content. The DataSource is always set on the Main report. Everything via designer, no need for coding. So I'd like to see such a possibility in telerik reports.

The suggested solution - with the bindings http://www.telerik.com/forums/how-to-bind-the-datasource-of-a-subreport-in-the-designer is technically wrong. It assumes that the child report knows at which level he resides inside the main report. The child report (or it's binding) should have not such info embedded. Let's see on an example. Let's have a dataset:
User.Address
User.PostalAddress
User.Wife.Address
User.Wife.PostalAddress

The dataset should be bound to the main report. The main report should have 2 sub-reports (address and postal addres). It can have an another sub-report (for wife data) which then would again have 2 sub-reports inside for addresses.

Using the technically wrong solution, the addresses for the main user should have a binding expr. like: =ReportItem.Parent.DataObject.xy and the wife's addresses have like: =ReportItem.Parent.Parent.DataObject.xy

There is a big problems with such a binding: the child must know the hierarchy of the data.

The technically clean solution is to have a dataset assigned to the main report. When adding a sub-report to the main report, via binding we should set the new data-source for the sub report. something like: MainReport.Data = dataSource. SubReportAddress = dataSourceOfTheCurrentReport.Address. SubReportWife = dataSourceOfTheCurrentReport.Wife and inside "wife report" the next sub-report for address address should have a binding again like: SubReportWifesAddress = dataSourceOfTheCurrentReport.Address

I have a Graph with a Legend with Position LeftCenter. I want the text of the legend to be Right-aligned.

However, neither the Series > LegendItem > Style > TextAlign gets respected, nor the GraphLegend > Style > TextAlign. the text is always left-aligned.

Current version of Telerik Reporting allows to generate reports on linux environment using the gdipluslib but it doesn't support the print.

Would be nice to implement the print of the report via CUPS or IPP protocol.

Report is working fine in local IIS but not in IIS server. See error details below.

Error creating report instance (Report = 'AttendanceTagging.trdp').
An error has occurred.
A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 64. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.

The old report that I have has the following table cell definition:

<TableCell RowIndex="2" ColumnIndex="0" RowSpan="1" ColumnSpan="1">
  <ReportItem>
    <TextBox Width="7.471cm" Height="0cm" Left="0cm" Top="0cm" Value="= Iif(Fields.NutzungMaschinenbreite &gt; 0, Fields.NutzungMaschinenbreite, &quot;&quot;)" Name="Z2S3NutzungMaschinenbreite" StyleName="">
      <Style TextAlign="Center" VerticalAlign="Middle">
        <BorderStyle Default="Solid" />
        <BorderWidth Default="2px" />
      </Style>
      <ConditionalFormatting>
        <FormattingRule>
          <Style BackgroundColor="LightGray" />
          <Filters>
            <Filter Expression="Fields.Eigene" Operator="Equal" Value="= True" />
          </Filters>
        </FormattingRule>
      </ConditionalFormatting>
      <Bindings>
        <Binding Path="Height" Expression="= Iif(First(Fields.Typ) = 'H', '0,66cm', '0,003cm')" />
        <Binding Path="Visible" Expression="= Iif(First(Fields.Typ) = 'H', 'True', 'False')" />
      </Bindings>
    </TextBox>
  </ReportItem>
</TableCell>

Since the Height of the inner TextBox is '0cm' the corresponding processing cell becomes Null when processing the Table and the Reporting code throws a NullReferenceException:

[NullReferenceException: Object reference not set to an instance of an object.]
   Telerik.Reporting.Processing.Table.ForEachCell(Action`1 action) +121
   Telerik.Reporting.Processing.Table.MeasureDataItemContent(IMeasureContext context, SizeLU availableClientSize) +622
   Telerik.Reporting.Processing.DataItem.MeasureContent(IMeasureContext context, SizeLU availableClientSize) +86
...

The error message may be made more informative, stating that the table row should be at least '10px', as the designer warns in design time.

Add progress bar that indicates when the report would be fully rendered.

The version is encoded twice in each QR code; once at the top right and once mirrored at the bottom left. A comparison of the boxes tells which is the version.

The Reporting tool doesn't mirror the version correctly at the bottom left, and some strict barcode readers don't recognize the barcode correctly.