Inside telerik designer for reports actually if you wish to use an RGBA color, you would need to manually write it.
And generally color choise / picking its a little old style.
-> Would be nice to modernize the UI for color management and implement a COLOR PICKER.
Currently, to customize the report engine, for example to add some custom user functions, we have to either use the app config or provide a IConfiguration to ReportProcessor constructor, which seems to set a static field for all reports, and on top of that we have to provide a whole assembly (which will load ALL non-private static methods, I did try to use typereferences instead of assemblyReferences, but that doesn't seem to work for custom functions).
Meanwhile all we needed was to expose a handful of functions. Our current workaround is to have a whole assembly dedicated to that.
It'd good to be able to:
- Specify either a single class or individual methods through the library API (e.g. reportProcessor.AddCustomFunction("name", (arg) => ...); or reportProcessor.AddCustomFunctions(typeof(MyCustomFunctions);)
- Avoid using static state (it limits how the library can be used and, more importantly, tested)
- Maybe have a way to provide a Service Provider, that Telerik library would use to create services/classes and pull IConfiguration from, especially those we provide, that way the custom functions could use services from our application, rather than using all static methods.
Thank you,
<Telerik.ReportViewer.BlazorNative.ReportViewer
@ref="reportViewer"
ServiceType="ReportViewerServiceType.REST"
PageMode="PageMode.SinglePage"
ServiceUrl="@(ServiceUrl)"
@bind-ReportSource="@ReportSource"
AuthenticationToken="@(AuthToken)"
ScaleMode="(ScaleMode)ReportSetItem.Report.ScaleMode"
@bind-ParametersAreaVisible="@ParametersAreaVisible"
Scale="1.5">
</Telerik.ReportViewer.BlazorNative.ReportViewer>
The variable, ParametersAreaVisible, is set to false. The report viewer is still showing the parameters area. I went back to the designer and set all parameters to Visible = false. When I did this, the parameters area is not displayed.
The report viewer should respect what is bound to ParametersAreaVisible.
I have projects on .NET Core and I want to use the System.Text.Json serializer that is the new default, but reporting relies on Newtonsoft.Json.
---
ADMIN EDIT
There are two approaches that can be taken right now to solve this:
OPTION 1: define separate endpoints (services, projects) for the different tasks - they can still use the same database layer through a shared project, depending on the architecture you have. This would let you have separated services with the appropriate serializers without custom attributes and code (see below). For example, create a separate project for the reporting REST services.
OPTION 2: add some custom decoration on the endpoints so you can choose which serializer is used on each, you can find some examples here: https://stackoverflow.com/questions/59650907/how-to-configure-two-json-serializers-and-select-the-correct-one-based-on-the-ro - the point being to register a serializer depending on the endpoint based on your own code rather than let the framework put one in for all endpoints.
NOTE: This would be a breaking change.
---
Hi, in the wpf report viewer, the date picker in the parameter's zone don't have a "Today's date button". The standalone report designer have the "Today's date button".
Date picker of the report designer :
Date picker of the wpf report viewer :
Is it possible please to add the "Today's date button" for date pickers in the wpf report viewer?
Thanks a lot!
Currently, there is no natural way to disable picturebox errors. Sometimes we do not care to know that the image wasn't found, especially when the error shown severely damages the look of the report, stretching and pushing things out of the way. The image URL may be built via parameters, pointing to a large folder where photos of a given employee may or may not exist. It took multiple unhelpful support tickets, many headaches and days of research to finally find an obscure post by a private individual with an undocumented custom solution that worked.
Is there a way to have the linear gauge display a value above the indicator?
The Uri user function can be selected from the functions list in the expression editor of the designer but when the report is previewed the following error message is shown.
The expression contains undefined function call Uri()
Just a simple quality-of-life improvement, middle-click on the tab should close the report - doing exactly the same thing as clicking the "X" button in the tab. Seems the majority of tabbed UIs follow this convention.
We have an app that loads a list of reports. When a report is selected, a report viewer page is loaded. It contains a set of parameters. In this stage, we get a http 400 error because it is the hitting the GetParameters endpoint right away. The user has not selected any parameters. It should only hit this endpoint when the user has selected the parameters and runs the report.
This is not the behavior in the HTML viewer.
In the images attached, the Initial Load image is the error we get when the report viewer page is loaded.
The Report Source is the payload when the GetParameters endpoint is called. As you can see it's empty since the report is not ran yet.
In the Running image, the error is when the user runs the report.
It would be very convenient if we could just right-click on a calculated field, such as "Period" in the screenshot below, and be able to modify the existing expression (within a context window)
Instead, I now have to do the following:
1. Click on the Data Source
2. Click on the ellipses button within the "Calculated Fields" property of the Data Source's properties
3. Find the desired expression within the "Edit Calculated Fields" window
4. Click on the expression's drop-down and select <Expression>
That's a lot of clicks for something that is done rather frequently!
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
I have been forcing my webservice data source into a workable solution for making GraphQL requests. Right now in order for us to use GraphQL, we have to build out the request manually with a string such as the following:
{"query: "query GetSomeResult($input: Int!) {result {id name}}", "variables": "{"input": @parameter}" }
While this is a normal way to hand craft a GraphQL request, the issue I have is that it shouldn't need to be that hard. Also I get no intellisense or suggestion in regards to the data returning. This means that when I try to bind data to a text box, I have to visually validate that the [=Fields....] is actually correct by looking at the GraphQL query and at the code base. I would love to see the ability to to just say have a set of standard api technologies we could implement from such as GraphQL queries, GRPc queries, or any other contract style request. I would expect that the data source logic would be smart enough to parse the query (at least for GQL) and be able to provide reccomendations.
Also a major issue we have had is in being able to pass that data source to subReports, or dealing with any nested objects such as a user.address.addressLine1 would not be able to be found if address is a nested values like the following
user: { address: { addressLine1 } }
At the moment it's only possible to have your reports in old-fashioned projects.
It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).
Currently, when you design a report with SqlDataSource, ObjectDataSource, etc. you need to have access to the corresponding database, assemblies, etc. to see the fields and use the drag-and-drop functionality of the report designers.
The requirement is to embed the corresponding schema in the report or designer to let the report creator access the data source fields even without these external resources.
As an example, in the WebServiceDataSource the report creator may use inline JSON rather than connecting to the Web Service. This saves time and resources required for establishing the connection that is in fact not necessary for design purposes.
Almost any object can be set to grow (CanGrow = True). Which makes the object grow if the text is too long.
I believe you need a function for making the text fit inside the object.
“ShrinkToFit = True”
This would shrink the text so that it fits inside the object. So if the font size is 20 and a long text wouldn’t fit inside the object, the font size would shrink until it fits.
Today we need to set several conditional formatting rules for this and it’s far from perfect.
Hi Team,
I see you have written this custom example for using EntityFrameworkCore and SQL to act as a source of report storage (not cache storage).
This is a request to do the same but using the Azure Storage File Shares client library for .NET - Azure for .NET Developers | Microsoft Learn SDK to host the TRDP files.
For example:
ReportSourceResolver = new AzureStorageReportSourceResolver()
Thank you,
Mike
Hi Team,
Is it possible to remove dll version and report designer path from Creator and Producer metadata tags. We got this requirement from our client. I am posting the remediation steps shared by our client below-
Is this possible to remove Telerik Reporting 14.1.20.618 (http://www.telerik.com/products/reporting.aspx) highlighted part and keep Telerik Reporting only?