It would be really useful if EntityDataSouce was updated to support Entity Framework Core contexts. EF Core depends on Standard 2.0 so can run on .NET Core or the full framework.

It would be great if you could introduce the ability to create custom reusable color palettes in Telerik Report Designer, so I don't have to declare the same set of colors for each chart I need them.

If you have a lot of graphs in your report then it is more convenient to change the color palette one place.

Images taken with a mobile device are sometimes displayed in PictureBox  rotated by 90, 180 or 270 degrees. The reason is that whenever a photo is taken, the device saves its current accelerometer orientation into a corresponding Exif tag with the image metadata, so this info is then read and taken into account by our Report Designer.

When using the Report Viewer under WinForms, Print Preview allows the user to scroll through all report documents.  I.E., everything in the document map.  However, when using the Wpf version you cannot.  In the Wpf version, the user must use the Document map to select and scroll through each particular area.

For large reports containing multiple documents, this is tedious.  

Please make the Print Preview functionality for the WPF control match that supported by the WinForms control.

I had compare crystal report and Telerik report on rendering similar dataset. (LARGE dataset)
Crystal report renders much faster on showing the initial page (viewer) by almost 50% compare to Telerik html5 viewer. (almost 10,000 pages)
Crystal report renders much faster on generating PDF file by also 50%.
Also Crystal report telling the total page on the initial rendered page., while on Telerik report (html5 viewer) it on shows pages that are already cache (and show caching progress.) It would be nice if it show the total pages then shows in the status notification the progress of caching.

We create many legal forms, which use nested ordered lists. In htmlTextBox for reporting, we'd like to apply styles like upper-alpha, lower-alpha, etc to the ol tag. Currently, the only numbering for an ol is 1, 2, 3. CSS ability to set the style at depth (like ol ol) would be best.
<ol>
<li>1. text</li>
<li>2. text
  <ol>
  <li>a. text
     <ol>
          <li>i. text</li>
          <li>ii. text</li>
      </ol>
  </li>
  <li>b. text</li>
  </ol>
</li>
</ol>

We use Telerik's report books extensively - and find that to be a very powerful way to create dynamically generated reports.

The feature request is: if a report's datasource doesn't fetch any rows don't add a blank page to the report book.

Use only components from KendoUI for Angular. It would be understandable that such report viewer would provide less features, but it would remove dependency from jQuery and KendoUI for jQuery.

Hello,

We use WebServiceDataSource with OData query in our reports. Sometimes OData can through an exception.

In our case, we have added Web Service DataSource and set this OData query for its Service Url:

https://services.odata.org/V3/Northwind/Northwind.svc/Products(1)?$select=ProductName1

If you see the query, it is selecting "ProductName1" property of "Product #1". But "ProductName1" property does not exist (correct property name is "ProductName"). When we use Postman for the OData query above, it shows an error which you can see from attached picture (ErrorWhenWeUsePostman.PNG, "Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'"). From the second picture (TelerikReportingGeneralError.PNG, "An error has occurred... Response status code does not indicate success: 400 (Bad Request).") you can see the result of our test report (in html5 report viewer) that has the same OData query.

The question is when we preview our report (in html5 report viewer) how can we show the error message that OData sent instead of showing Telerik reporting general error?
Instead of this message:

An error has occurred while processing Report 'TestReportWithWebServiceDataSource': Response status code does not indicate success: 400 (Bad Request).

This OData error message should be handled and shown on browser (html5 report viewer) when previewing report:

Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'

FYI: We are using Telerik Reporting version 15.0.21.224.

This is my post on Telerik forum related with this: How to get internal error message from Custom Report Resolver

Thank you,

We need our reports to have editable text fields where data can be entered into the pdf document and printed.

See also the Forum thread export pdf with editable text areas.

Currently, the desktop viewers don't allow adding custom headers to their requests to the service.
In HTML5-based web viewers, this is possible through the AjaxPrefilter event.

Keeping nested tables on the same page causes huge empty spaces on multiple pages. This is definitely not a proper way for implementing such things. This feature request is caused by this forum response: http://www.telerik.com/forums/nested-tables-makes-page-breaks-in-pdf

Please do not reply with 'grouping', crosstab or other proposals because data grouping has other limitations. Also please note that nested table is pretty common simple scenario for situation when data already is grouped which is almos always the case of ObjectDataSource scenarios.

Impact: Currently these half-empty pages cause report to look low-quality which is not acceptable for our clients. 

The property DataSources is internal in the Report class. When manipulating the datasources of a report it's easier to have access to this collection than to go through all the elements en report parameters to check for datasources

It's currently not possible to define in the HTML5 Report Viewer "per Report" the available Export formats. It's also not possible to alter the List in the given JS Events because the List of PDF,XLS,etc is loaded on MouseOver in the menu.

Would be great to have some kind of options, array list in the widget options to define what export formats are displayed.

Kind regards, Otto.

Why is it that the telerik report designer is locked down and cannot be used as a set of controls in a custom application as any other telerik control. We would like to use the report designer controls in an application we make to give it our look and feel and so we can give it the functionality we require. Why limit your customers by locking down your report designer. One of the great things about telerik is a great set of products and customer support. If we had a way to get at the Telerik.ReportDesigner.Core.dll we can figure our where the controls are and display them in our app. I don't understand the marketing behind the locked down report designer. How does it benefit your customers? You can still have a locked down designer for those customers that don't want to customize it. Providing access to Telerik.Reporting.Core.dll will give your customers the ability to customize the report designer to their needs. Telerik sells controls that customers use to make applications that they sell, so whats the difference with the designer? 

If there are parameters which are not mandatory, the reports automatically when loaded. In actual scenarios, there may be a lot of data being processed as the parameters may be empty. Developer should have an option on report level, say, AutoRun as true or false. The developer could decide if report needs to auto run.

Thanks,
Jai

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

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.

The OpenXML renderings in .NET work with DocumentFormat.OpenXml 2.7.2 - 2.20.0

When upgrading to version 3.0.0 the Word rendering throws the following exception:

CSharp.Net7.Html5IntegrationDemo Error: 0 : System.TypeInitializationException: The type initializer for 'Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentHelper' threw an exception.
 ---> System.TypeLoadException: Could not load type 'DocumentFormat.OpenXml.Packaging.ImagePartType' from assembly 'Telerik.Reporting.OpenXmlRendering.2.7.2, Version=17.2.23.1114, Culture=neutral, PublicKeyToken=a9d7983dfcc261be' due to value type mismatch.
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentHelper..cctor()
   --- End of inner exception stack trace ---
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentHelper.CreateMainPart(WordprocessingDocument package)
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentBuilder.CreateMainPart()
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.DocumentBuilder.CreateBodyLayout()
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.ReportWriter.WriteDocument(DocumentBuilder documentBuilder, LayoutElement layoutElement)
   at Telerik.Reporting.OpenXmlRendering.Wordprocessing.WordprocessingWriter.WriteEndElement(LayoutElement source, ElementPageInfo pageInfo)
   at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.EndElement(LayoutElement element, ElementPageInfo info)
   at Telerik.Reporting.Paging.PageEndElement.OutputToPage(IPageHandler handler)
   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()
An error has occurred while rendering the report: System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Threading.ManualResetEventSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.SpinThenBlockingWait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.InternalWaitCore(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(CancellationToken cancellationToken)
   at Telerik.Reporting.Paging.PageCompositionBase.SeparateThreadOutputBehavior.Finish()
   at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
   at Telerik.Reporting.Paging.PagerBase.Telerik.Reporting.Paging.IPager.CreatePages(IPageHandler handler, LayoutElement root)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)
*** Render Report #0 "ReportCatalog" DONE in 00:00:00.2183346 ***

CSharp.Net7.Html5IntegrationDemo Error: 0 : An error occurred while rendering the report in separate thread: System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Threading.ManualResetEventSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.SpinThenBlockingWait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.InternalWaitCore(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(CancellationToken cancellationToken)
   at Telerik.Reporting.Paging.PageCompositionBase.SeparateThreadOutputBehavior.Finish()
   at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
   at Telerik.Reporting.Paging.PagerBase.Telerik.Reporting.Paging.IPager.CreatePages(IPageHandler handler, LayoutElement root)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)
   at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(Report report, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback)
   at Telerik.Reporting.Processing.ReportProcessor.RenderCore(ExtensionInfo extensionInfo, IList`1 processingReports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Processing.ReportProcessor.RenderCore(String format, IList`1 reports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
   at Telerik.Reporting.Services.Engine.ReportRenderer.Render(ReportRendererArgs args)
   at Telerik.Reporting.Services.Engine.Rendering.RenderWithCulture(ReportRendererArgs args)
   at Telerik.Reporting.Services.Engine.Rendering.ThreadFunc(Object o)

I would prefer my OpenXML rendering to work with the latest DocumentFormat.OpenXml version.