Under Linux, when the font is set with Conditional Formatting some of the TextBoxes may be rendered with different that the expected Font in Docx. Other TextBoxes set with the same rule to the same font are rendered correctly.

The same report rendered in Docx under Windows produces the correct document.

I have an asp.net core web app that works fine running from VS 2019 and IIS Express. However, if I run it under a docker windows container, there's an error when deserializing the xml .trxd file.

Exception thrown: 'System.TypeInitializationException' in Telerik.Reporting.dll
Exception thrown: 'System.Reflection.TargetInvocationException' in System.Private.CoreLib.dll
Exception thrown: 'System.Reflection.TargetInvocationException' in System.Private.CoreLib.dll
Exception thrown: 'System.MissingMethodException' in Telerik.Reporting.dll

This is only happening when running in a windows docker container.

Please do some testing with this configuration.

The pinch zoom feature on mobile devices is not working as expected.

• On iOS devices, the zooming is fidgety, zooming is not accurate where the pinching gesture occurs.
• On Android devices, Zoom In on the report will take the page to the top left. 

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