Currently, you can select multiple report items with the CTRL when you run the Web Report Designer on Mac, however, this is interpreted as a right-click. Please, check the attached video.
The correct behavior should be by using CMD.
I display the WPF Report Viewer control in a closable tab. To free the resources I invoke DisposeViewerResources on tab close as described here: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/wpf-application/disposing-the-report-viewer-resources
However, I see the following dialog every time. There is no way to capture this error or suppress the dialog.
Some corner case page size value force report processing to create an invalid page clipping during paging.
Workaround: If you encounter such scenario, please experiment with changing the page size to another value, which is close to the original one.
Please add the Web Report Designer Item Template for VB.NET projects too
Consider adding functionality that allows for loading Assets into the Asset Manager from code.
I would prefer to store assets in a database and load them up for a user.
Makes more sense than randomly loading them from whatever computer you are working on.
I am trying to get a basic example of the Web Report Designer working following the guide here but I keep getting this error message
in the console, I can see these errors
here is the razor page that contains the WebReportDesigner
@page "/report-designer"
@attribute [Authorize]
@using Telerik.WebReportDesigner.Blazor
<WebReportDesigner DesignerId="wrd1"
ServiceUrl="/api/reportdesigner"
ToolboxArea="new ToolboxAreaOptions() { Layout = ToolboxAreaLayout.List }"
PropertiesArea="new PropertiesAreaOptions() { Layout = PropertiesAreaLayout.Categorized }" />Any assistance would be appreciated
I am currently investigating including the Telerik Reports in our products but when I load the Web Report Designer it loads a theme which is overwriting our custom theme.
Is there any way to prevent this so that we keep our custom theme?
If you add the 'kendo.common.min.css' that is required for the Html5 Viewer to the page with the Web Report Designer, the latter Menu styles get broken.
Due to this, if you need to have both the viewer and the designer in the same project and cannot have scoped styles, the appearance of one of them will be broken.
In some scenarios, it would be helpful to have the path to the report available, for example, as a Global Object, so that you may use it in the Expressions.
Here is a use case. The PictureBox resolves relative paths with respect to the report's folder. Currently, if you want to check whether an image that is in the report's folder exists by its name only, you need a custom user function. If you know the report's folder, you may do this with System functions.
In some cases, the textbox width will be nearly but not enough to fit the whole string and as a result, the textbox will grow and will thus push the items below it further down.
In Page Sections, this may even result in some of the items that are near the bottom not being displayed at all.
It would be great if there was a warning when the width is not enough so that such scenarios are avoided.
There should also be an option to disable the warnings.
It takes 2+ seconds between "info" polls to the server. This should be a much smaller interval. Maybe .5 or .25 seconds.
Telerik's own ReportClient example shows a 500ms interval between info polls...
private static byte[] GetDocument(ReportClient restServiceClient, string instanceId, string documentId)
{
bool documentProcessing;
do
{
Thread.Sleep(500);// wait before next Info request
documentProcessing = restServiceClient.DocumentIsProcessing(instanceId, documentId);
} while (documentProcessing);
byte[] pdfDocumentBytes = restServiceClient.GetDocument(instanceId, documentId);
return pdfDocumentBytes;
}Bindings to the TitleStyle property of a ToC section result in the following error:
Bindings error - The value of property 'TitleStyle' is null
Currently, when you set SplitWorksheetOnPageBreak to True, the Excel Sheet name is formed from the DocumentName or ReportName and the number of the page.
It would be very helpful if the report authors can manipulate these names with Expressions.