Boolean parameter checkbox is with a small size in the HTML Viewer with Kendo SASS theme created with ThemeBuilder.

The current workaround is to use the following CSS to set the width and height of the checkbox:

.k-checkbox{
   width: 16px !important;
   height: 16px !important;
}

The XAML rendering extension, used by the WPF Report Viewer, by default checks for invalid characters while writing the XAML page contents. When the data that will be rendered on the page contains invalid Unicode characters, an exception is thrown and the report is not rendered.

The current solution is to introduce a UserFunction that parses  the string contents and strips the invalid characters, but implementing and maintaining this approach requires more efforts from the developer.

An option in the XAML Device Information Settings that disables the check for invalid characters, would work in most scenarios without having to write a dedicated UserFunction. By default this option will preserve the current behavior, i.e. the characters checking will be performed, but the developers will have the ability to disable it on their own discretion.

When a report is saved in the Web Report Designer, a popup appears confirming that the report was successfully saved. However, it is visible for far too long and blocks users during this time.

This feature request is to add an 'ok', 'hide' or 'close' button to these types of popups so the user can dismiss it.

Thank you,

Shannon

When there is a textBox report item placed in a report page header/footer section with a text color styling applied to the textbox, the text color is not respected in the Excel export.

This happens only when the native excel page header/footer is used.

The property of the Graph Numerical Axis CrossAxisValue is listed in the Bindings editor dropdown of the Graph Coordinate System. When I set it, the report displays an error that the property does not exist.

I found out that the property is obsolete.

My ReportLibary has 174 reports. When I tried to convert them at once with the Standalone designer, it converted a few of them and threw the following exception (showing part of the Stack Trace):

Application: Telerik.ReportDesigner.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
   at System.Windows.Forms.BindingSource.get_Count()
   ...

Converting the reports in smaller portions was successful.

It seems that only one event is being removed when disposing, there are 3 more, can these 3 also be removed when disposing? 

Also if possible remove the kendoSplitter resize event:

Please, add a .zip or .7zip with the following content from the Telerik Reporting folder:

• all runtime assemblies- everything from the Bin folder without the Design folder and VS<Version> (for example VS2019, VS2022, etc) folders
• Html5 folder
• License Agreements folder
• Silverlight folder
• Wpf folder

In Reporting msi installer no verification is performed if the user exists and has create database permissions on remote database SQL server. No message is shown if AdventureWorks database creation fails.

1. Start Reporting .msi installer.
2. Agree with License.
3. Click button "Examples setup".
4. Enter database server name on remote machine with user with only public server role.
5. Click Next.
6. Click Install.

Expected: Message that database creation failed on step 4,5, or 6.
Actual: Installation proceeds and finishes. AdventureWorks database is not created.

 In the Word rendering, there is sometimes space between the footer and the body of the document.

Bindings to the TitleStyle property of a ToC section result in the following error:

 Bindings error - The value of property 'TitleStyle' is null

It takes 2+ seconds between "info" polls to the server. This should be a much smaller interval. Maybe .5 or .25 seconds.

Telerik's own ReportClient example shows a 500ms interval between info polls...

        private static byte[] GetDocument(ReportClient restServiceClient, string instanceId, string documentId)
        {
            bool documentProcessing;
            do
            {
                Thread.Sleep(500);// wait before next Info request
                documentProcessing = restServiceClient.DocumentIsProcessing(instanceId, documentId);
            } while (documentProcessing);

            byte[] pdfDocumentBytes = restServiceClient.GetDocument(instanceId, documentId);

            return pdfDocumentBytes;
        }

In some cases, the textbox width will be nearly but not enough to fit the whole string and as a result, the textbox will grow and will thus push the items below it further down.

In Page Sections, this may even result in some of the items that are near the bottom not being displayed at all.

It would be great if there was a warning when the width is not enough so that such scenarios are avoided.

There should also be an option to disable the warnings.