The pdf documents generated with Telerik Reporting are not compatible with the BlueBeam Revu PDF editing tool.

For example, if we select a text and try to change the font size, the selected text inverts (upside down) and flies to the left of the document. 

The labels of the axes and data points of a Bar chart are not correctly placed in PDF rendering when using .NET Core. The Graph is rendered on multiple pages. The appearance on the first page is correct and deteriorates on the next pages.

In.NET Framework, the same report is rendered as expected.

Digital signature (certificate) in Word and Excel files.
In the same way that today it is possible to sign the PDF.

Something needed to make the document official.

Tranks

When the SqlDataSource wizard uses a connection to a non-MSSQL database, which is registered in a Report Server instance, previewing the results on the "Preview data source results" page will throw an exception.

Hi there,

I would like to make a feature request for your Reporting Tool that would greatly improve the way we are able to create Custom Report Parameters Front-End for our application.
Currently we have access to a number of properties against each Report Parameter such as whether it is Visible or whether or not it is a MultiValue control as well as some other options you are well aware of. I would like to request that you allow the ability to create custom properties against a Report Parameter.

Currently when we build up our custom parameter interface we use the Visible field whether or not to Show the parameter and we use the MultiValue parameter to switch between multi select and single select inputs and we determine the type of control we use based on the Type property. Up to now we have managed ok with the built in properties but we are starting to find some limitations that would easily be resolved if we could add whatever properties we want to a Report Parameter.

An obvious example is if we had more complex control options for the various Report Parameters we might like to add a property that has the name of the control to use rather than having to guess which control to display based on the Type of the Parameter. Or if we have multiple parameters that depend on each other we can add a property that tells us what the hierarchy for the parameters is. That would allow us to know on the front end that one Parameter depends on another parameter.

The reason I believe adding custom properties is the best approach is because then the sky is the limit with how I can customise those options and my own customer parameter interface.

Is there any chance this request could make it into your product roadmap? I believe it is a feature that could be very beneficial not just for us but to all your customer.

Thanks,

Aaron

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.