The parameters' area splitter's expand icon gets hidden when the area is shrunk.
I have a TextBox that is rotated at 270 degrees. Its width in some cases is not enough to accommodate the incoming value. I expected it to grow vertically (i.e. in width) in this case. However, its width didn't grow. It just cut the content.
I noticed that if I increased the height of the TextBox, the content was wrapped horizontally.
It would be very useful if the report parameters of all the HTML5-based report viewers become accessible from the report viewer widgets.
For example, we are currently working on a report that has a custom button that sends the current parameters to an API and "signs" the current report (e.g. saves a string in the database and displays it afterward in the report).
We would like to validate if the currently shown report matches the report parameters but are unable to find a valid solution for this scenario.This is the outcome in the Standalone designer:
This is the outcome in the WPF viewer:
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:
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.