When I try to export a ReportBook to TIFF as explained in Exporting a report to a multi-document format, I receive an exception related to the file '.../report/image.tif' that cannot be created.
When I create the folder '.../report', there is another exception message:
'The process cannot access the file '...\report\image.tif' because it is being used by another process.'
The above error was thrown the second time the ReportProcessor tried to access the 'CreateStream' method from the code snippet in the above article. The 'image.tif' file is created and contains only the first report from the ReportBook.
With version 15.0.21.112 the last exception is not thrown and the 'image.tif' file contains all reports from the ReportBook.
Whenever we start our application we're getting the following warning.
WARNING in ./node_modules/@progress/telerik-react-report-viewer/dist/dependencies/telerikReportViewer.kendo.min.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from 'xxx\node_modules\@progress\telerik-react-report-viewer\dist\dependencies\kendo.custom.min.js.map' file: Error: ENOENT: no such file or directory, open 'xxx\node_modules\@progress\telerik-react-report-viewer\dist\dependencies\kendo.custom.min.js.map'
webpack compiled with 1 warning
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.
Currently, when using External Stylesheets in the reports, the engine tries to first load the stylesheet as an embedded resource of the assembly. If it fails to load it from the assembly, a message is written to the trace along the lines of:
ESS: Attempt to load ExternalStyleSheet from EmbeddedResource from assembly Telerik.Reporting, Version=19.0.25.211 with resource name styles.xml is unsuccessful.
After this, the engine will try other ways to resolve the stylesheet such as from URI and if it succeeds, the report will render as expected.
This can create confusion because looking at the trace, one might think that there were errors with the rendering of the report because the stylesheet did not load but it was actually successfully loaded with one of the other approaches.
It would be better to write the errors to the trace only if the stylesheet does not load after all attempts.
The PDF with enabled Accessibility looks fine in the Adobe PDF reader.
However, when I check it with the PAC tool, it shows in the logical structure the Detail section first, then the Page Header, and then the Page Footer.
1. The data member list in "Choose a data member" (step 2) of the objectDataSource wizard in the Web Report Designer does not appear to be in alphabetical order as it is in the Standalone Report Designer. When there are many data members it is hard to pick the one you want when not ordered alphabetically.
2. For a data member that returns a DataSet result, a table row has to be returned for the design time feature to generate a data schema. In the Standalone Report Designer a returned row is not necessary, all that is required is a returned DataSet with a Table with Columns setup. It would be easier when using Web Report Designer to not require data returned to establish the data source data schema. In the WidgetDataSource a fake row is returned for the sake of having the data schema generated.
3. In the Web Report Designer objectDataSource wizard, once the "Preview data source results" (step 4) are ready and the Finish button is clicked, there is another call to the data source member but instead of using the Design-Time Values for the member, the values in the Value column appear to be used. If report parameters are already assigned to the data source parameters the string of the Value (e.g. "= Parameters.StartDate.Value") is used instead of the report parameter value. I think the data member call to generate the data schema should be the Design-Time Values again. In order to get the data schema generated I had to use the same values for Value column as in the Design-Time Values value. After the data source parameters are assigned to report parameters then it breaks the generation of the data schema later when the report is opened again in the Web Report Designer and there is an error (e.g. Error An error occurred while loading the data schema for "Widgets". ("Message"."String was not recognized as a valid DateTime.").
4. In the Report Previewer for the Web Report Designer there does not seem to be a way to provide a null value to a nullable data source parameter. For the GetWidgets member the FromEffectiveDate parameter is a nullable DateTime. After the data source is configured the data source parameter DataType is set to String, it did not resolve to nullable DateTime. Even after I change the data source FromEffectiveDate parameter to DataType of DateTime it cannot accept a null value from a DateTime report parameter, it seems to be interpreted as string instead of null. In the Standalone Report Designer there is no problem having a DateTime report parameter passing null to a nullable DateTime data source parameter; after reconfiguring the data source in the Standalone Report Designer the DataType for the data source parameter is <DataType>System.Nullable`1[System.DateTime]</DataType> instead of <DataType>System.DateTime</DataType> as from the Web Report Designer.
5. This is not a specific objectDataSource wizard issue but rather a general issue in the Web Report Designer. I cannot create a Report Parameter with the same name as a data source parameter or CSV data source field. Trying to do so results in an error message (Error Could not change property 'Name'. Name 'FromEffectiveDate' already exists). This issue can be demonstrated in the Web Report Designer Demo page: create a parameter for the yearDataSource data source, try to create a report parameter with the same name to get the error. Using report parameter names that are also data source parameter names works fine in the Standalone Report Designer.
The data member list in "Choose a data member" (step 2) of the objectDataSource wizard in the Web Report Designer does not appear to be in alphabetical order as it is in the Standalone Report Designer.
When there are many data members it is hard to pick the one you want when not ordered alphabetically.
In the Web Report Designer's objectDataSource wizard, once the "Preview data source results" (step 4) are ready and the Finish button is clicked, there is another call to the data source member but instead of using the Design-Time Values for the member, the values in the Value column appear to be used.
For example, If report parameters are already assigned to the data source parameters the string of the Value (e.g. "= Parameters.StartDate.Value") is used instead of the actual report parameter value. I think the data member call to generate the data schema should be the Design-Time Values again. In order to get the data schema generated I had to use the same values for Value column as in the Design-Time Values value.
After the data source parameters are assigned to report parameters then it breaks the generation of the data schema later when the report is opened again in the Web Report Designer and there is an error (e.g. Error An error occurred while loading the data schema for "Widgets". ("Message"."String was not recognized as a valid DateTime.").
I cannot create a Report Parameter with the same name as a data source parameter or CSV data source field. Trying to do so results in an error messagŠµ
(Error Could not change property 'Name'. Name 'FromEffectiveDate' already exists).
This issue can be demonstrated in the Web Report Designer Demo page: create a parameter for the yearDataSource data source, try to create a report parameter with the same name to get the error.
Using report parameter names that are also data source parameter names works fine in the Standalone Report Designer.
Hello,
the search results in a PDF generated with report is not correct. Again...
Please fix this bug and add this scenario to your tests.
Steps: Search for a text in a pdf.
Hi,
In Desktop Designer, I create a very simple Report with :
- a JSON datasource mapped to the report
- a Table with two colunms
I want to duplicate this table, so I select it and do a copy. After that, I select the detailSection and do a paste. The pasted table, in the Report Explorer look fine, but in the designer view it is not the case. And if I compare the TRDX files, an entire section is missing (the <Cells> section).
Attached files :
- Multi-zone.trdx : Before copy/paste
- Multi-zone-2.trdx : After copy/paste
- Screenshot.png : screenshot of the Designer where you can see the two tables and the Report Explorer
Thank you
PS: In additional informations, I specify ASP.NET MVC as Project Type, but it is not relevant.
I have the chance to use a 27", 5120 x 2880 monitor, with text on Windows set to 200%.
The problem with Telerik Report Designer is that the icons in the report designer are very small and barely usable:
- Panel icon to move it.
- Table icon to move it.
- The open / close icons in the Report Explorer.
Also the zoom indicator at the bottom left of the screen, where the text part is too small to display the current zoom.
After updating to Telerik Reporting v19.0.25.211, the relative path provided to the UriReportSourceResolver is no longer working.
For example, I used to provide only the name of the directory with the reports(e.g. "Reports") to the UriReportSourceResolver, and if there was such a subdirectory inside the project's base directory, the reports were successfully resolved.
This is no longer the case with v19.0.25.211. With this version, I have to provide the absolute path to the "Reports" directory for it to work.
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.