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
ReportViewer will resize correctly when the window is resized by manually dragging the frame, but when 'Maximize' or 'Restore Down' buttons are used, the resize will not occur.
If continues scrolling is turned on, the next page to load in will be in a different size because it will be in the correct size, while the first page remains in the previous size.
A work-around is to add this codesnippet to the HTML, which will trigger the resize:
function resizeViewer() { $("#reportViewer1").trigger('resize'); }
window.addEventListener("resize", resizeViewer);
On numerous occasions I've found that the need to float or rearrange the designer windows such as the data explorer, properties or group explorer window would be very beneficial to my workflow.
As well this request should consider the ability of the data explorer and report explorer to be decoupled so as both can be visible simultaneously.
Normally table's of context are formatted with roman numerals. Based on the responses in the forum, only Arabic numbers are allowed. Request the ability to change the formatting of the rule numbers and restart the page numbering after the TOC.
Generate and distribute packages built against .Net 5.0.
Currently .Net 5.0 RC1 and .Net 5.0 RC2 are announced. The official version has been announced on 10th of November.
For our Customers a major drawback to creating form type reports (Invoices, Purchase Orders etc.) using Telerik Reporting is the inability to show vertical dividing lines between data columns in the 'Detail' section of the report that extend all the way down the page to the Page/Report footer. We were able to do this with Crystal Reports. But we plan to migrate all our Crystal reports to Telerik.
When configuring a WebServiceDataSource in the Web Report Designer in ASP.NET, upon previewing the data there is an error '404 Not Found". The same web service was successfully resolved by the Standalone designer and in the ASP.NET Core demo.
The data source fields were visible and usable in the designer also under ASP.NET Web Report Designer.