Currently, there is design-time support for the WinFoms Report Viewer in the VS Designer only when the project targets .NET Framework. I need this functionality to be supported in .NET WinForms projects as well.
In some cases, the engine will not render the graph and will instead display the message
The current NumericalScale settings would result in more than 1000 labels which will make the scale unreadable. Please set the axis/ grid lines visibility to False or change the corresponding property.
The reason to see this or similar messages is that the selected LabelStep, MajorStep, or MinorStep scale property has a value that is too small and the processing engine will violate the previously mentioned constraint numbers.
The issue is fixed by manually correcting the values for those properties but I wish that the automatic configuration would be better.
This way I will have a better control on how and when the user functions are resolved at runtime.
When there is a combination of Arabic and English text in any control and if the font family is set to "Calibri", exporting to PDF results in the following error in the stack trace:
Telerik.ReportDesigner.exe Error: 0 : System.NullReferenceException: Object reference not set to an instance of an object.
at Telerik.Documents.Fixed.Fonts.OpenType.Tables.MultipleSubstFormat1.Apply(GlyphsSequence glyphIDs)
at Telerik.Documents.Core.Fonts.OpenType.Tables.Lookup.Apply(GlyphsSequence glyphIDs)
at Telerik.Documents.Fixed.Fonts.OpenType.Tables.ChainedSequenceContextFormat3.ApplySubstitution(GlyphInfo glyphInfo)
at Telerik.Documents.Fixed.Fonts.OpenType.Tables.ChainedSequenceContextFormat3.Apply(GlyphsSequence glyphIDs)
at Telerik.Documents.Core.Fonts.OpenType.Tables.Lookup.Apply(GlyphsSequence glyphIDs)
at Telerik.Documents.Core.Fonts.OpenType.Tables.Features.FeatureInfo.ApplyLookup(Lookup lookup, GlyphsSequence glyphIDs)
at Telerik.Documents.Core.Fonts.OpenType.Tables.LangSys.Apply(GlyphsSequence glyphIDs)
at Telerik.Documents.Core.Fonts.OpenType.OpenTypeFontSourceBase.ApplySubstitutions(UnicodeRange range, List`1 glyphInfos)
at Telerik.Documents.Core.Fonts.OpenType.OpenTypeFontSourceBase.TryGetGlyphIds(String text, UInt16[]& glyphIds)
at Telerik.Reporting.Pdf.PdfFontDictionary.AddChars(String text)
at Telerik.Reporting.Pdf.Rendering.PdfRenderer.DrawString(String text, PdfFont pdfFont, IBrush brush, RectangleF rect, Boolean rightToLeft)
at Telerik.Reporting.ImageRendering.CanvasPdf.DrawRegularChunk(String text, StringChunkContext context)
at Telerik.Reporting.ImageRendering.CanvasBase.DrawStringMultiline(String s, StringChunkContext context, Boolean isFinalTextChunk)
at Telerik.Reporting.ImageRendering.DocumentBase.WriteText(String text, RectangleF bounds, IFont font, Color foreground, TextFormat format, MatrixBase transform, Boolean isFinalTextChunk)
at Telerik.Reporting.Writing.TextBoxWriter.WriteContent(DocumentWriter writer, TextBox textBox, ElementPageInfo pageInfo)
at Telerik.Reporting.Writing.ProcessingContentElementWriter`1.WriteElement(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(TextBox textBox)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.Paging.PageElementsLayer.OutputToPage(IPageHandler handler)
at Telerik.Reporting.Paging.PageContent.Output(IPageHandler handler)
at Telerik.Reporting.Paging.PageCompositionBase.OutputPageContent(Stopwatch stopwatchOutputContent, PageContent pageContent)
at Telerik.Reporting.Paging.PageCompositionBase.<>c__DisplayClass124_0.<CreatePageContentOutputTask>b__0()If we change the font family to "Arial" the report is exported to PDF correctly.
My report contains a Crosstab with HTMLTextBox. When exporting to PDF, the document looks fine.
In Word export, the HTMLTextBox content is partly hidden and shows only when I manually extend the corresponding item height.
We use some cascading/dependant parameters and, in some cases, these have their "value" property (initial/default) value unset, generally to prevent the viewer auto-run as well as to give the user a chance to select first.
The dependant parameters have their Value properties set to the ValueMember field(e.g. =Fields.value) so when the cascading parameter is selected, the dependant will have a valid value set.
However, the "missing or invalid parameter" still shows that the dependant parameter has an invalid value.For example:
In the WebReportDesigner, when resizing a table cell on the designer-Element (NOT through the properties area), the Units of width and height are always reset to pixel.
The selected unit should not change when resizing the table cell/column/row.
The Web Report Designer lets the user change the size of a TextBox inside a Table cell from its Properties. The change is also visualized in design time. For example, if the TextBox is enlarged, it sticks outside the table.
The above change is not respected in the preview of the web designer.
I would expect such a resize to be impossible, as in the Standalone Designer; or the entire table column/row to change its size accordingly.
The report items that have explicitly set background in the report definition are not highlighted by the Search functionality of the viewer when their content matches the search.
Reproducible with Blazor Native Report Viewer.
Partially reproducible with HTML5 Viewer - the highlighted (when selecting the item in the Search list) class is applied but the shaded is not.
The workaround is to use the following styles on the page with the viewer:
<style>
.trv-report-viewer-wrapper .trv-search-dialog-highlighted-result {
background-color: rgba(0, 35, 102, 0.3);
color: #fff;
background-image: none;
}
.trv-report-viewer-wrapper .trv-search-dialog-shaded-result {
background-color: rgba(255, 140, 0, 0.3);
}
</style>
If the Telerik.ReportViewer.WinForms.ReportViewer.ReportSource property of the WinForms Report Viewer is null, besides displaying a message that no report has been loaded, the parameters area is also visible.
The parameters area shouldn't be visible when no report is selected, only the message should be displayed in the viewer's viewport.
The design-time preview of an HtmlTextBox located in a data item throws a null reference exception when it has a conditional formatting rule that changes the appearance of the HtmlTextBox based on the RowNumber data function. This function cannot be executed successfully during design time as the data is not available yet.
Since this issue is also related to the preview during design time, it does not affect the actual report preview either.
The design-time preview of the PictureBox throws a null reference exception when it has a binding that changes its value based on one of the fields from the data source. The preview incorrectly tries to respect this binding which will not work in design time as the data is not fetched at this point. Instead, the design-time preview should use the default value from the Value property of the PictureBox, which is what the standalone designer does.
This does not affect the actual report preview.
Watermark Images with higher than the report rendering DPI are displayed clipped in PPTX rendering.
In PDF, preview of the designers and DOCX the same watermark is shown as expected.
If the DPI of the image is 96 as the default Windows machine DPI used for rendering, the Watermark is displayed correctly also in PPTX.
I have successfully installed the ODBC and OLEDB providers for Visual FoxPro 9 and they appear in the Windows 32-bit ODBC Data Sources under System DSN.
The drivers are discovered when I use Standalone Report Designer x86 from 17.2.23.1114 and older ones built against .NET Framework 4.0.
The same drivers are not found on the same machine when I use Standalone Report Designer x86 from 18.3.24.1218 built against .NET Framework 4.6.2.
All of my report parameters have their AutoRefresh setting set to False, and the parameters do not depend on each other, they are not cascading parameters. The parameters have available values.
If I change the value of one of the parameters, despite the above settings, all of the other parameters' data is re-retrieved(even if those parameters are not visible).
This causes issues because the "Preview" button is disabled until the parameters are refreshed, and makes the UX bad since if the connection is slow, the end-users will have to wait for the parameters area to refresh after changing any parameter value.
DPI Awareness Settings are not applied when printing from the ReportProcessor in .NET where the configuration is provided in the constructor.
However, if I manually invoke the SetProcessDpiAwareness function before triggering the printing, the DPI is successfully updated.
Just like the HTML5 Report Viewer, it will be easier to embed the Web Report Designer in an application if it wasn't necessary to manually add the kendo script to the page.
I have a use case which requires me to record data whenever a report is printed. In pursuit of this, I am trying to replace the build in Print() tool and replace it with my own.
I have read this documentation which shows how to remove and reorder the buttons well enough, but it does not support adding a new tool all-together. Javascript event listeners will not work for me because ultimately what I want to do is accomplish a database write, which would be insecure through javascript.
I have been able to establish a workaround by following this documentation and creating a button *outside* of the ReportViewer, however, I would still like to find a way to put the button inside of the ReportViewer toolbar if possible.