When an item has borders applied and the report is exported to PDF, the border lines "stick out" at the joints. The image below illustrates this.

Some additional information about the issue:

• The issue was first introduced in the R1 2017 SP2 Release.

• The issue seems to appear only in Chromium-based browsers.
  • Microsoft Edge -> reproducible
  • Google Chrome -> reproducible
  • Opera -> reproducible
  • Mozilla Firefox -> not reproducible
  • Adobe Acrobat -> not reproducible

• The borders "stick out" differently based on the zoom level. In some zoom levels, there are no issues, in others the borders "stick out" at the bottom, right, etc. 

Error: Unable to cast object of type 'Telerik.Reporting.Processing.Expressions.ProcessingEvalProvider' to type 'Telerik.Reporting.Expression.IValueObject'

is thrown on previewing the data source results in the WebServiceDataSource when the Runtime or Design time expressions are left completely empty or the runtime value is a report parameter with an empty Value property.

When generating PDF/UA files, we need to have special objects that are read by an internal system but ignored by screen readers. This cannot be achieved with the existing functionality.

It would be beneficial if we could configure reports so that specific objects inside the generated document are ignored by screen readers. For example, by setting a special value to the AccessibleRole property of a text box. 

When certain fonts are used, the text of reports exported to PDF looks different between the Skia and GDI rendering engines, even if the fonts are fully embedded.

For example, if the TT Norms font is used and the report is exported to PDF (full font embedding) with both engines, the document rendered by Skia is much larger and looks different than the GDI-rendered document.

Since upgrade to openXML 3.0.0 we get exceptions at runtime when we want to create a report in XLS.

While a feature request has been filed here: https://feedback.telerik.com/reporting/1631967-openxml-renderings-should-work-with-documentformat-openxml-3-0-0-and-newer one could argue it is a bug. Anyway, i raise this issue here to have some extra attention to it.

System.TypeLoadException
  HResult=0x80131522
  Message=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.
  Source=Telerik.Reporting.OpenXmlRendering.2.7.2
  StackTrace:
   at Telerik.Reporting.OpenXmlRendering.Spreadsheet.Worksheet..ctor(Workbook workbook, WorksheetPart worksheetPart)
   at Telerik.Reporting.OpenXmlRendering.Spreadsheet.Workbook.AddWorksheet()
   at Telerik.Reporting.ExcelRendering.Report.Render(IWorkbook workbook)
   at Telerik.Reporting.OpenXmlRendering.Spreadsheet.SpreadsheetReport.Telerik.Reporting.Processing.IRenderingExtension.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.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.<>c__DisplayClass47_0.<RenderReport>b__0(SingleStreamManager sm)
   at Telerik.Reporting.Processing.ReportProcessor.RenderReportSafe(Func`2 renderCallback, String format, IRenderingContext renderingContext)
   at Telerik.Reporting.Processing.ReportProcessor.RenderReport(String format, ReportSource reportSource, Hashtable deviceInfo, CancellationToken cancellationToken)
   at Telerik.Reporting.Processing.ReportProcessor.RenderReport(String format, ReportSource reportSource, Hashtable deviceInfo)
   at Indato.Reporting.TelerikReports.<>c__DisplayClass1_0.<RenderReportAsync>b__0() in C:\Users\leosiepel\Source\Workspaces\Indato\Indato-Main\Indato.Reporting\TelerikReports.cs:line 42
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)

Conditional formatting property already exists in Telerik.Reporting.LegendItem class however does not exist on Telerik.Reporting.GraphLegend.

Would be great to have a ConditionalFormatting property into the Telerik.Reporting.GraphLegend to allows to perform bindings on this element.

Exemple of use case not possible currently: Bind the GraphLegend.Position property with an expression.

The Standalone Report Designer allows users to add Anchoring to an item even if its container has KeepTogether set to False. This is not valid and can break report definitions without a warning.

The reports can be fixed by editing the XML code of the definition manually and setting the KeepTogether property to True.

running your https://demos.telerik.com/reporting in Chrome 77.0.3865.75, when trying to print the following error is returned:

Refused to execute script from 'https://p.adsymptotic.com/d/px/?_pid=16218&_psign=0aa5badf92527f7732e22463d6fa4dbc&coopa=0&gdpr=0&gdpr_consent=&_puuid=1ddd0495-ceb5-4cd4-b879-03f7c6be269b' because its MIME type ('image/gif') is not executable.

and nothing happens.

wasn't this fixed in your latest update?

is there a workable solution for this issue?

Requesting a feature to allow some sort of selection feature on the "Send Mail Dialog". The issue that we're having is if the user needs to email a report to 5 or 10 people it becomes very daunting, ugly and difficult for them to achieve this without making errors in typing out every single email.

Also, in most cases the user might not know the individuals email official email address in the organization so they have to go look up every single one. If there was a drop down selection or an auto predict while typing then once clicked it grouped up the name to make it look cleaner and easier for them to find the email addresses that would be wonderful. Here's an example of what it looks like right now.

Not sure if you are aware of this but the new property SkipBlankPages in 2021/R1 will result in a corrupt (unopenable) PDF/XLS if the report contains no data.

The output used to be a blank report.

This behaviour is fixed by setting the Value to 'False' but this now requires the developer to remember to set this value on each new report. Perhaps the default should have stayed as 'False' and those who wish to remove blank pages could set it to true.

We are aware the property is set to true by default.

We have now had to modify (and subsequently retest) > 100 reports.

The generator should probably not create a 'corrupt' file in these cases.

Kind regards

I have DataSource assigned to my report, which content is displayed in its Detail section. The Page sections have some static content. The SkipBlankPages property is set to False.

When the data set received by the report is empty, the static content in its Page sections is not displayed in Interactive View. In PrintPreview the Page Header/Footer content is displayed as expected. When the data set returns valid data, the Interactive view displays everything as expected.

The report processing is stopped and the following message is shown when trying to preview a report that uses one of the available DataDirect drivers in a .NET Core application.

The same report can be previewed successfully in a .NET Framework application.

When editing a report that has a watermark of type BackgroundOverlay with Sizing set to TopLeft, the design time preview of the watermark does not scale with the zoom level correctly.

The preview displays correctly only at 100% zoom level.

To prevent questions that I can't answer: I'm an end user for this product. I DO NOT have the ability to look at or update code related to the tools integration. So please ignore my answers to Product Version and Target Framework. They were required before I was allowed to post this ticket. 

The uploaded report has 6 components. 

Two panels (one containing multiple objects, the other only containing one object [hb2])

4 text boxes each with some bindings.

The two key components to look at for the issue are hb and hb2. Both these objects are identical and both have the same bindings for height and top.

From my math hb2 is correctly positioned and sized by hb has been pushed down. The only difference is that other objects are in the container for hb.

Without any containers, hb and hb2 are positioned incorrectly.

I'm doing all this because the vertical alignment for text boxes was not working, once I exported to PowerPoint.

What I expected was that the Top value would only depend on the container holding the component and the components' top value. I did not expect it to be dependent on a mixture of variables from other components also held within the same container.

When a system tells users they should look into the report parameters as the reason the report isn't displaying.  It's reasonable for your users to believe you aren't misleading them. 

The report viewer error message misleads users.  In reality the parameters are correctly configured and it the repot URL could be wrong.  Or a variety of other issues are at play; for instance, a problem with you connection string will also return the "Unable to get report parameters" error message.  I'd like to see this error message at minimum changed to "report can't display."   It's better to throw out a generic message vs having users spend hours or days troubleshooting the report parameters.  Better yet a proper catch/validation system put into place please.