When using specific tables the query builder of the Standalone designer may fail with the message:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelManager.CreateEntity(String path)
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelManager.FindOrCreateEntity(String path, Boolean refreshRelations)
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelManager.AddProperty(Property sourceProperty)
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelTreeViewController.TreeViewAfterCheck(Object sender, TreeViewEventArgs e)
   at System.Windows.Forms.TreeView.OnAfterCheck(TreeViewEventArgs e)
   at System.Windows.Forms.TreeView.WndProc(Message& m)
   at Telerik.Reporting.Design.Common.Controls.TreeViewEx.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The SQL script for creating the table to reproduce the issue is given in the Object Reference error on using Query Designer forum post.

When exporting to Excel Worksheet, the CheckBox item is rendered as Excel Picture. If the machine settings are higher than the default 96 DPI (100%), the checkbox image is generated with incorrect size and the produced Excel file is corrupted.

I am suggesting a global 'this.value' option for conditional formatting. This approach would allow quick use of the fields value to be the basis of the condition. In reports that use complex and sometimes lengthy calculations, this is would be a huge timesaver.  This feature would also have to work with your current 'cut and paste' rule feature.

If I had to create individual rules for each box on a page, or a series of rules for each box to do multiple colors it would be a very unproductive use of time for me.

Putting my one project in perspective, if I had to do it with rules.

Right now, I have over 300 fields with 2 rules each, which is 600 rules to write and that is only about 75% of what I need on a single page of the report. This is a serious time burn activity just to get something like a conditional formatting to work on the value of the field. The rule approach might be good if the solution has less than 10 fields, but to have the shear numbers I do, I do not think it rule creation for each field is a viable solution.  Another solution proposed was to create additional calculated columns. The problem with this is that the data source already has 100+ columns and I would hate to add any more fields (at least 100+ more), due to performance considerations.

I love the Telerik reporting solution do to the instant flexibility in my apps, but the conditional formatting is lacking especially if you use it for large analysis reports with comparisons that the client (and myself) would like coloring of the text to 'see' things easier.

Telerik: See ticket 1462207 as reference

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.

Current Behavior

1. Open the Standalone Report Designer.

2. Navigate to the Open Menu.

3. Select the Computer Tab.

4. Observe the available list of folders under the Computer Menu.

5. Navigate to the Options Menu.

6. Change the Default Working Directory.

7. Navigate to the Open Menu.

8. Observe the Available Folder and the directory will not be listed.

9. Select the Browse Button.

10. Observe the open folder is not the expected Default Working Directory from Step 6.

Expected Behavior

It would be nice to remove the previous folder from the Standalone Report Designer Open Menu.

Hi there,

I was wondering if you had in the Pipeline/road map a Report Designer integrated into Visual Studio for .NET Core?

And also if there is an ETA?

If I can add my +1 to this would be appreciated.

Regards,

Mark

Currently, the row/record delimiter when exporting to CSV is taken from the environment. This way, the same CSV document will have different line separators when exported from Windows and Linux.

It will be very useful if the row delimiter can be specified in the device information settings the same way the field delimiter can.

When the Report is shown in the HTML5 Interactive viewer, you can move the mouse over the cells in the Hyperlink column. When a cell has the mouse cursor hovering over it, a gray border is drawn around the cell.

The problem is that this gray border is partially covered by the Background color of the next cell.

I have a few reports in which I have a multivalue parameter that renders a ListView control.  However, when the user clicks on "Select All", only the 1st value is sent to the server.

Also, if some of the values have default values when defining the Report parameter and one of them is the 1st value, then ALL values are pre-selected when the Report renders. However, when the user clicks "Preview", again only the 1st value is sent to the server.

The above happens when I reference Kendo ( kendo.all.js) 2020.2.513 in the project. With Kendo 2020.1.114 the viewer works as expected.

Provide NuGet package with UI for WPF NoXaml dependencies for adding it to the project that hosts WPF report viewer: