I have a Multivalue Report Parameter in the report that gets fed by a data source and may have more than 1000 selectable values. It is a ComboBox.

When I search and select a value from the dropdown, the selected value may not be passed with the reportSource of the viewer if I click directly the Preview button, without clicking outside the selection popup first. The issue occurs randomly. If I click outside the popup first, the values are passed correctly. I cannot reproduce the issue with less selectable items.

We upgrade to 17.2.23.1010 and after going through the report Upgrade Wizard we are getting this error for the CheckBox item:

Error CS0266 Cannot implicitly convert type 'System.Drawing.ContentAlignment' to 'Telerik.Drawing.ContentAlignment'. An explicit conversion exists (are you missing a cast?)

The option for creating a new connection in the SqlDataSource of the WRD is disabled in the .NET Framework implementation of the ReportDesignerController.

When using the SqlDataSource component with a stored procedure that has an IF-ELSE condition which selects a different set of columns depending on whether the condition is true or false, the returned data schema is always as if the condition is evaluated to true.

While the schema is wrong, if I manually type the fields, at runtime, they get resolved correctly but it is inconvenient.

I had a report book with only a TOC report and when I previewed it, I was met with an "Object reference not set to an instance of an object" exception which did not make it clear what was causing the issue losing me a lot of time in debugging.

Once I added a report to my ReportBook the issue was resolved, however, the error message should be more meaningful.

I am rendering Telerik reports (version 17.2.23.1010) with custom code on Linux Docker in .NET 7 with SkiaSharp. When I have Grouping in the Report, I receive the following exception:

An unhandled exception has occurred while executing the request.
      System.PlatformNotSupportedException: System.Drawing.Common is not supported on this platform.
         at System.Drawing.ToolboxBitmapAttribute..ctor(Type t, String name)
         at System.Reflection.CustomAttribute._CreateCaObject(RuntimeModule pModule, RuntimeType type, IRuntimeMethodInfo pCtor, Byte** ppBlob, Byte* pEndBlob, Int32* pcNamedArgs)
         at System.Reflection.CustomAttribute.AddCustomAttributes(ListBuilder`1& attributes, RuntimeModule decoratedModule, Int32 decoratedMetadataToken, RuntimeType attributeFilterType, Boolean mustBeInheritable, ListBuilder`1 derivedAttributes)
         at System.Reflection.CustomAttribute.GetCustomAttributes(RuntimeModule decoratedModule, Int32 decoratedMetadataToken, Int32 pcaCount, RuntimeType attributeFilterType)
         at System.Reflection.CustomAttribute.GetCustomAttributes(RuntimeType type, RuntimeType caType, Boolean inherit)
         at System.Attribute.GetCustomAttributes(MemberInfo element, Type attributeType, Boolean inherit)
         at System.ComponentModel.ReflectTypeDescriptionProvider.ReflectGetAttributes(Type type)
         at System.ComponentModel.ReflectTypeDescriptionProvider.ReflectedTypeData.GetAttributes()
         at System.ComponentModel.TypeDescriptor.DefaultTypeDescriptor.GetAttributes()
         at System.ComponentModel.TypeDescriptor.GetAttributes(Type componentType)
         at System.ComponentModel.ReflectTypeDescriptionProvider.ReflectedTypeData.GetConverter(Object instance)
         at System.ComponentModel.TypeDescriptor.DefaultTypeDescriptor.GetConverter()
         at System.ComponentModel.TypeDescriptor.GetConverter(Type type)
         at System.ComponentModel.PropertyDescriptor.get_Converter()
         at Telerik.Reporting.Serialization.ObjectReader.ReadProperty(Object obj, PropertyDescriptor prop, Type propType)
         at Telerik.Reporting.Serialization.ObjectReader.ReadProperties(Object obj)
         at Telerik.Reporting.Serialization.ObjectReader.ReadObject(Type type)
         at Telerik.Reporting.Serialization.ObjectReader.ReadXmlElement(String name)
         at Telerik.Reporting.Serialization.ObjectReader.ReadCollection(Object collection)
         at Telerik.Reporting.Serialization.ObjectReader.ReadProperties(Object obj)
         at Telerik.Reporting.Serialization.ObjectReader.ReadObject(Type type)
         at Telerik.Reporting.Serialization.ObjectReader.ReadXmlElement(String name)
         at Telerik.Reporting.Serialization.ObjectReader.Deserialize(IResourceHandler handler)
         at Telerik.Reporting.XmlSerialization.XmlSerializerBase.Deserialize(XmlReader reader, IResourceHandler resourceHandler)
         at Telerik.Reporting.XmlSerialization.XmlSerializerBase.Deserialize(Stream stream, IResourceHandler resourceHandler)
         at Telerik.Reporting.XmlSerialization.ReportXmlSerializer.Telerik.Reporting.ReportSerialization.IXmlSerializer.Deserialize(Stream stream, IResourceHandler resourceHandler)
         at Telerik.Reporting.ReportPackager.UnpackageDocument(Stream packageStream)

Without Grouping the report is rendered fine on Linux.

On Windows, everything runs fine as well.

I am getting an error message, even when setting the culture manually to 'en-US', that the culture 'aa' is not found. Tried other approaches to get the culture manually installed, but there shouldn't be a reason your code is pulling all cultures when 'en-US' is the one being manually set by my code and in the report designer.

In the Desktop Report Designers, you may display the Text of the Tooltips on several lines by adding new lines (\n) inside the text.

In the HTML5 Viewrs, the new lines are ignored and the text is displayed on a single line. You may work around this by replacing the new lines with <br /> elements. It would be much easier for the users if this is done in the code of the viewer instead.

On .Net 6, exporting html5 produces multiple html files including a single report having multiple pages are split into multiples. Could we please have the feature similar to MHTML export in the previous .net versions supported. This is a breaking change when upgrading to .Net 6. 

Thanks!

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.

After updating the Telerik Reporting packages to v17.2.23.1010 and opting out to still use the Gdi graphics engine, when I attempt to render a report to PDF on Linux, the rendering fails with the following error:

Error: 0 : An error occurred while rendering the report in separate thread: System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Reporting.Paging.PageCompositionBase.<>c__DisplayClass87_0.<CreatePages>b__0()
   at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
   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.Services.Engine.ReportRenderer.Render(ReportRendererArgs args)
   at Telerik.Reporting.Services.Engine.Rendering.RenderWithCulture(ReportRendererArgs args)
   at Telerik.Reporting.Services.Engine.Rendering.ThreadFunc(Object o)

When the service of the Web Report Designer is running in a .NET Framework application, the preview page of the WebServiceDataSource component displays [object Object] instead of the data string.

The WRD front end expects the ReportDesignerController's PreviewWebServiceData(DataSourceInfo) method to return stringified JSON but instead, it currently(R3 2023) returns a JSON.

As a workaround, the method can be overridden so that the string result is returned instead:

        public override IHttpActionResult PreviewWebServiceData(DataSourceInfo dataSourceInfo)
        {
            var baseResult = (ResponseMessageResult)base.PreviewWebServiceData(dataSourceInfo);
            var jsonString = baseResult.Response.Content.ReadAsStringAsync().Result;

            return Ok(jsonString);
        }

When a report that has no significant content is added to a report book, an invalid entry inside the report book's ToC is added. The page number shown is zero and trying to navigate to the page throws an error "Resource with name ... not found."

Need to allow Excel Export with 10.1.16.615 version on FIPs enbled

Hi Team,

I had tried with the provided post as below with DocumentFormat.openXML.dll verison (2.5) but not working .

please help to resolve this ASAP.

===

Based on what you described and the ticket info, I am assuming that you are getting this error when you render a report in the Excel 97-2003 (XLS) format. Is that correct?

Unfortunately, this is a known limitation of the Excel 97-2003 rendering, and exporting a report to XLS in FIPS-enabled environments will fail. Considering this, I suggest choosing one of the following options for exporting reports to Excel:

• Exporting the report to the newer XLSX format. (See exporting in XLSX)
• Disabling FIPS.

If choose the first option, you can disable the older Excel rendering format so that it is not available as an option when the report is displayed in a report viewer. For example, the following code can be put into the web.config/app.config of the project:

<configuration>

  <configSections>
    <section
        name="Telerik.Reporting"
        type="Telerik.Reporting.Configuration.ReportingConfigurationSection, Telerik.Reporting"
        allowLocation="true"
        allowDefinition="Everywhere"/>
  </configSections>

    ...

  <Telerik.Reporting>
    <extensions>
      <render>
        <extension name="XLS" visible="false">
        </extension>
      </render>
    </extensions>
  </Telerik.Reporting>

   ...

</configuration>

I hope this helps, please let me know if you have any additional questions. Thank you for trying Telerik Reporting!

Regards,
Dimitar
Progress Telerik

Is there a way to have the linear gauge display a value above the indicator?

The following exception can be thrown when setting the Value of a PictureBox to an invalid type:

System.ArgumentException: You can assign System.String, IImage, System.Drawing.Image or SkiaImage objects only.
at Telerik.Reporting.PictureBox.set_Value(Object value) 

This is misleading because an object of type System.Drawing.Image is not supported when using the Skia graphics engine. Passing an SKImage does not work either due to an error in the processing stage.

If you need to use a System.Drawing.Image object or an SKBitmap instance, you can take advantage of the DrawingFactory class.

When using the HTML5 Report Viewers, if I override the GetDocumentFormats() method of the ReportsController and return a localized list, the export dropdown in the toolbar is still populated with the default values.

On the other hand, the available export formats list is respected in the email dialog.

In both scenarios, the dropdown with the rendering formats should respect the overridden method's return value.