Approved
Last Updated: 17 Jan 2020 14:13 by ADMIN
Created by: Ludek
Comments: 0
Type: Bug Report
1

Print functionality doesn't work in React application.

Steps to reproduce:

1. You may use the sample project from How to use HTML5 Report Viewer in React Application article.

2. Run the project and click on Print.

The following error can be seen in the browser's console: Resource interpreted as Document but transferred with MIME type application/pdf: "https://demos.telerik.com/reporting/api/reports/clients/a7fdd020ec4/instances/3f53abd1614/documents/c3923e685e6d6ebefb3d11?response-content-disposition=inline".

Approved
Last Updated: 16 Jan 2020 13:44 by ADMIN
Created by: Hal
Comments: 10
Type: Feature Request
19
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.
Approved
Last Updated: 16 Jan 2020 07:42 by Niek
It would be good if the table headers can be frozen.  This can  be really useful in case of a big report which is displayed on a single page.
Approved
Last Updated: 16 Jan 2020 05:40 by Sami
The TOC is missing when the report is exported programmatically to Word in .NET Core application
Approved
Last Updated: 14 Jan 2020 11:26 by ADMIN
When providing both inline JSON and service Url to WebServiceDataSource, in design time the data is requested from the service instead of being taken from the inline JSON to reduce the network load.
Approved
Last Updated: 13 Jan 2020 09:10 by ADMIN

Currently the Web Report Designer (WRD) can only work with reports stored on the server where the WRD Web API service is hosted.

A nice addition would be the option to select a local TRDX/TRDP file from the client file system and upload it to the server, when opening a new report for edit.
When saving such report there should be an option to download it to the client's file system as well.

With this approach the open/save operations will more closely resemble those of the standalone report designer.

Approved
Last Updated: 10 Jan 2020 15:56 by ADMIN

Under Linux, when the font is set with Conditional Formatting some of the TextBoxes may be rendered with different that the expected Font in Docx. Other TextBoxes set with the same rule to the same font are rendered correctly.

The same report rendered in Docx under Windows produces the correct document.

Approved
Last Updated: 06 Jan 2020 10:07 by ADMIN
Created by: Paul Johnson
Comments: 0
Type: Bug Report
1
If you export a table in RTF whose content is longer than 1 page, in the exported document the whole table will be placed on one page only and the rows that are in the end might not be seen.
Approved
Last Updated: 12 Dec 2019 14:13 by Adam
The problem is not getting the error via Dot Net programming, but the complete layout destruction of the report as a result of the fact that a picture (in our case a thumbnail of a provider) is unavailable. Catching the report error is not an option. It is too complicated and even if we succeed  in obtaining the error, it will be very complicated to remove the unavailable url on the fly and re-render the report again. 

This seems to be a "known issue" for about 8 years!

My question: Is it possible to keep the remaining report "intact" if such an error occurs? This shouldn't be too difficult for the development team..
Approved
Last Updated: 09 Dec 2019 17:55 by ADMIN
The report is not exported correctly in PDF when the Font is Sakkal Majalla and Text Align is Right. If you set the Text Align to left, everything works as expected.
Approved
Last Updated: 05 Dec 2019 15:22 by ADMIN

When merging the ReportViewer's WPF theme dictionaries from the DLL in App.xaml, the VS2019 Designer fails due to a problem with a ZoomComboBoxStyle definition.

This causes all Telerik UI for WPF control's styles fail to load in the Visual Studio designer.

WORKAROUND

Instead of App.xaml, merge the ReportViewer's theme dictionary closer to the control.

For example in the ReportViewer's direct parent:

<Grid>
<Grid.Resources>
<ResourceDictionary>
<ResourceDictionary.MergedDictionaries>
<!-- Moved from app.xaml -->
<ResourceDictionary Source="/Telerik.ReportViewer.Wpf.Themes;component/Themes/Summer/Telerik.ReportViewer.Wpf.xaml" />
</ResourceDictionary.MergedDictionaries>
</ResourceDictionary>
</Grid.Resources>

<tr:ReportViewer x:Name="ReportViewer1" ReportSource="{Binding CurrentReport}" />
</Grid>

Approved
Last Updated: 05 Dec 2019 10:27 by ADMIN
Let the user configure whether the Standalone designer to start initially in Interactive or PrintPreview mode. Currently, it starts always in Interactive mode and this may cause slow down or even hanging if the previewed report is huge.
Approved
Last Updated: 04 Dec 2019 14:00 by Mark

Hello Telerik team!

In the attachment, there are two PDFs, generated by the same template (also in attachment): one built under Windows, another one - under Linux (Docker). See red boxes as defects on the screenshot:

Text wrap issues

Text wrap issues

Dockerfile fragment:

# MS TrueTypeFonts install
RUN wget http://ftp.de.debian.org/debian/pool/contrib/m/msttcorefonts/ttf-mscorefonts-installer_3.6_all.deb -P ~/Downloads
RUN apt install -y ~/Downloads/ttf-mscorefonts-installer_3.6_all.deb

RUN apt-get install -y libc6-dev
RUN apt-get install -y libgdiplus
RUN apt-get install -y libx11-dev
RUN rm -rf /var/lib/apt/lists/*

 

Please help us to resolve these issues in Linux.

Approved
Last Updated: 04 Dec 2019 10:13 by ADMIN

When you try to send the report through the SendMailMessage functionality but an exception is thrown, the report will disappear. If you click on Refresh and try again with fake data, the exception will be thrown but the report will remain. If you prefer to refresh it automatically, you can use the error event:


var viewer = $("#reportViewer1")
.telerik_ReportViewer({
    serviceUrl: "api/reports/",
    reportSource: {
        report: "Report Catalog.trdp",
    },
    error: function (e, args) {
        console.log("This event handler will be called after a page of the report is ready.");
        console.log("The error message is: " + args);
        viewer.refreshReport();
    },
    viewMode: telerikReportViewer.ViewModes.INTERACTIVE,
    scaleMode: telerikReportViewer.ScaleModes.SPECIFIC,
    scale: 1.0,
    enableAccessibility: false,
    sendEmail: { enabled: true }
}).data("telerik_ReportViewer");

Approved
Last Updated: 03 Dec 2019 12:00 by ADMIN
Sometimes when the width of the page is less than the one of the report (<13px). This content on the right side (the last 12px) will be not visible.
Approved
Last Updated: 27 Nov 2019 12:13 by ADMIN
Created by: Grzegorz
Comments: 1
Type: Feature Request
1
Dark theme is so much needed.
Approved
Last Updated: 26 Nov 2019 12:25 by ADMIN

StackTrace of the error:

 System.NullReferenceException: Object reference not set to an instance of an object.
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at Telerik.Reporting.Interfaces.LocalizationContext.GetString(String resx, String key)
   at Telerik.Reporting.SRDescriptionAttribute.get_Description()
   at Telerik.Reporting.Expressions.EnumContextManager.GetItem(Type enumType)
   at Telerik.Reporting.Processing.ReportExpressionContext.RegisterAllReportingEnums()
   at Telerik.Reporting.Processing.ReportExpressionContext..ctor(Type reportType, AssemblyRefManager assemblyRefManager)   at Telerik.Reporting.Processing.ReportParametersManager`1.CreateExpressionContext(Report report, IList`1 runtimeParameters, AssemblyRefManager references)
   at Telerik.Reporting.Processing.ReportParametersManager`1..ctor(Report definitionReport, IEnumerable`1 definitionParameters, IDictionary`2 reportSourceParameters, IDataProviderContext dataProviderContext, AssemblyRefManager references)
   at Telerik.Reporting.Processing.DocumentParametersManager`1.CreateManager(Report definition, IDataProviderContext dataProviderContext, IParameterValueParser parameterValueParser, IDictionary`2 rsParameters, AssemblyRefManager references)   at Telerik.Reporting.Processing.DocumentParametersManager`1.CreateManagers(IProcessingContext context, IParameterValueParser parameterValueParser)
   at Telerik.Reporting.Processing.DocumentParametersManager`1..ctor(ResolvedReportDocument resolvedReports, IProcessingContext processingContext, IParameterValueParser parameterValueParser)
   at Telerik.Reporting.Processing.ReportProcessor.ProcessReportSource(ReportSource reportSource, IRenderingContext context)
   --- End of inner exception stack trace ---
   at Telerik.Reporting.Processing.ReportProcessor.ProcessReportSource(ReportSource reportSource, IRenderingContext context)
   at Telerik.Reporting.Processing.ReportProcessor.ProcessReportSource(ReportSource reportSource, Hashtable deviceInfo, IRenderingContext context)
   at Telerik.Reporting.Processing.ReportProcessor.ProcessAndRender(String format, ReportSource reportSource, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Processing.ReportProcessor.ProcessAndRenderStateless(String format, ReportSource reportSource, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Processing.ReportProcessor.RenderReport(String format, ReportSource reportSource, Hashtable deviceInfo, CreateStream createStreamCallback, String& documentName)

Approved
Last Updated: 25 Nov 2019 12:27 by ADMIN
If the data retrieval class is implementing IDisposable, the engine never invokes Dispose method. This can result in unexpected and unwanted data caching. Consider to invoke the IDisposable.Dispose if the data retrieval class is referenced by type (this.objectDs.DataSource = typeof(MyDataLayer))
Approved
Last Updated: 20 Nov 2019 12:58 by ADMIN

If a table-based item (Table, List, Crosstab) does not fit in a single page and needs to occupy more than one page, its bottom border is not drawn on the first page and its top border is not drawn on the second (subsequent) page. This behavior is by design and its purpose is to help the users visually distinguish the table as a single item. The table has only one top and bottom border and they are displayed at the beginning and at the end of the table, regardless how many pages the table actually occupies.

Since users might find this confusing, a table should have a property controlling this behavior. The default state of the property will preserve the current rendering. If the user explicitly sets the property, then the table will draw its top and bottom borders on every page it occupies.

Approved
Last Updated: 15 Nov 2019 15:28 by ADMIN
Created by: Martin
Comments: 0
Type: Feature Request
2

As in Ticket with ID 1440072 requested we are looking for a funktionallity to send Reports via E-Mails with the WPF ReportViewer. As only the HTML-5 ReportViewer currently supports the E-Mail sending we would request the feature for WPF as well.

 

Best Regards,

Martin

1 2 3 4 5 6