Change the Font Name of a TextBox from Arial to Calibri
Go to another TextBox and change the Font Name from Arial to Calibri.
This is the error I get: "Could not change the property 'Name'. Name 'Calibri' already exists."
The same error occurs when trying to change multiple TextBoxes at once.
The design-time web service data source parameter values are not displayed in the Web Report Designer while correctly read by the Standalone designer.
The run-time web service data source parameter values are displayed as [object] rather than expressions.
Check this screenshot for clarity.
If you open https://demos.telerik.com/reporting/designer?_ga=2.145120566.369274565.1605642252-790264781.1600201366 the problem can be seen.
Select one of the TextBoxes such as TextBox1
Select the Layout > Size Properties of the TextBox
Try to change the Width to 3.5 in.
Notice the Width goes to 35 instead of 3.5
This is the same case for Location > Left & Top and Size > Height
When applying the property Docking with either of the following values will cause the Visual Studio Report Designer to squeeze the table down to 0 width:
While the value 'Right' will cause the table to be rendered outside of the report-section on the left side. This is reproducible with the example report CryptoCurrencies.cs.
I am currently using Reporting 13.2.19.1030.
The following error occurred while using Reporting.
'Non-Error promise rejection captured with value: Error shown. Throwing promises chain stop error.'
I looked up the cause of this error, and I was able to confirm the following article.
As explained in the above article, the error in Report Server (5.1.19.618) has been corrected to appear to be a significant error.
So I looked up the release note to see if this error was fixed in the Reporting product, but I couldn't find any related information.
Is this error corrected on the Report Server only and not corrected in Reporting? If so, when can it be revised?
It would be very helpful for us people that have been using Telerik Reporting in Silverlight (or WPF) applications to have access to a Report Viewer for Windows Store Apps (XAML). The future of Silverlight is unclear at least and there are many Line Of Business Applications currently running under Silverlight and I know of many developers that are looking to port their LOB apps to Windows Store Apps (or Universal Apps). The current HTML5 Report Viewer does not provide printing when it is implemented in browser window in Windows Store Apps so we cannot really offer this option to our customers.
In some cases, when the path of the file is used as a Value of the PictureBox, the WMF is not displayed in PrintPreview or in the printed report. The workaround is to embed the image by selecting the file as a Value:
1. Go to the Value property of the PictureBox and click on the three dots (...)
2. In the File name field, type *.* and Enter.
3. Select the WMF file.
I am using this to color the xaxis, but I notice, it changes the color of all items, so what I want is to color them individually based in a condition like this:
XAxis.Style.Color = IIf(ToolStatus=1,'Green','Red')
The problem all the text is in green not considering the condition individually by column.
The parametersAreaVisible property of the angular report viewer allows controlling the visibility of the report parameters area.
Currently, this property can only be set. Reading the property doesn't reflect the current visibility of the report parameters area.
While jquery can be used as a work around to determine the visibility of the report parameters area (by reading the width of the corresponding DOM element), a proper angular API would be nice.
When one item is selected, or multiple items are selected where they all have the same size, the Width and Height property is accessible and will be applied for all selected elements. If multiple elements are selected and they do not all have the same width and height, the property becomes blank, and you do no longer have access to the Width and Height property.
It would be great to still have access to the properties so a value can be applied for all selected elements.
When a section is disabled by setting the Visible property to false, the section remains visible in the designer without any visual indication that it is invisible when rendered. Adding such a visual indication would allow users to more easily see that it is disabled.
Having a cross over the section, making it disappear from the designer window, or showing somehow it is disabled would make it easier to understand, as currently the only way to check this is by reading the value of the Visible property in the Properties pane
