Sometimes I need to be able to allow the users to choose not only the date but the time as well when displaying DateTime report parameters in my reports. There is no out-of-the-box functionality to achieve this and I am forced to implement custom parameter editors - Creating and Using Custom Parameter Editors in HTML5 ReportViewer - Telerik Reporting.
I should be able to set whether a DatePicker or DateTimePicker widget should be used for DateTime parameters from the report viewer's initialization options, such as how I can change the editor for single/multi-value parameters in the HTML5 report viewers - HTML5 Report Viewer Options Overview - Telerik Reporting.
Hello,
I see from support threads that Telerik really resists any changes to their concept of CSV rendering. And I also understand the reasoning in not changing any default behavior due to its potentially unwanted effect on established customers.
That said, I wonder if the ability to exclude hidden objects (TextBoxes for example) has been proposed and is in the list of potential enhancements. I wouldn't mind if it required a configuration setting like NoHiddenObjects = True where the default is False.
Has that been considered?
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).
Add the ability to specify rounded corners for the border of TextBoxes, Pictures, Tables and all other similar controls.
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.
I understand that the ReportViewer has a very different paradigm from, say, the RadGridView. However, I believe they should and could be much more similar. With some fairly minor tweaks ReportViewer could be made to be a proper member of the C#/XAML/MVVM environment. Particularly what is needed is a binding to the data source, just like RadGridView's "ItemsSource".
I've begun a discussion in the forum about this topic at https://www.telerik.com/forums/reporting-and-mvvm. With Momchil's help I was able to create a workable solution for my scenario, but it required code that, in my opinion, I shouldn't have to write.
I'd be more that willing to chat about this further and provide more thoughts and details, but since we've made it all the way to 2024 without this being raised, I tend to assume the needs I've expressed may not be as universal as I'd assumed they would be.
Thanks!
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.
---
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
please please put OR operator in Report designer data-source query.
For years users request and ask same question and still (in 2021) Report designer doesn not support OR query.
You can manually enter OR operator in sql-query, but then you cannot use the designer. :(((
Currently, there is design-time support for the WinFoms Report Viewer in the VS Designer only when the project targets .NET Framework. I need this functionality to be supported in .NET WinForms projects as well.
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,
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!