Hello,
I can see that we can operate over a file definition using save, open, and save as. It would also be nice to be able to download the report definition as well.
When trying to duplex print a report that has odd page numbers, the next report's first page prints on the back of the previous report. We need the ability to conditionally insert a page break based on whether the report's (the group's) page count is odd or even. Since we don't have access to the global pagecount variable outside the footer, there is no way to use it to insert a page break into the body of the report. This seems like it would be such a common need with the desire by many to save paper that it would be an obvious feature to include in the product. Thanks.
The ObjectDataSource component in the Web Report Designer does not have complete design-time support. The major things that are missing:
It would be very helpful for us people that have been using Telerik Reporting in Silverlight (or WPF) applications to have access to a Report Viewer for Windows Store Apps (XAML). The future of Silverlight is unclear at least and there are many Line Of Business Applications currently running under Silverlight and I know of many developers that are looking to port their LOB apps to Windows Store Apps (or Universal Apps). The current HTML5 Report Viewer does not provide printing when it is implemented in browser window in Windows Store Apps so we cannot really offer this option to our customers.
Now you can do it by grouping several options, but what i want is to hide one by one.
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.
---
I am using this to color the xaxis, but I notice, it changes the color of all items, so what I want is to color them individually based in a condition like this:
XAxis.Style.Color = IIf(ToolStatus=1,'Green','Red')
The problem all the text is in green not considering the condition individually by column.
Implementing Drag&Drop for the Web Report Design is a major step toward feature parity with the Standalone Designer, and helps end-users leverage their established workflow when migrating to the Web Report Designer.
When a section is disabled by setting the Visible property to false, the section remains visible in the designer without any visual indication that it is invisible when rendered. Adding such a visual indication would allow users to more easily see that it is disabled.
Having a cross over the section, making it disappear from the designer window, or showing somehow it is disabled would make it easier to understand, as currently the only way to check this is by reading the value of the Visible property in the Properties pane
On numerous occasions I've found that the need to float or rearrange the designer windows such as the data explorer, properties or group explorer window would be very beneficial to my workflow.
As well this request should consider the ability of the data explorer and report explorer to be decoupled so as both can be visible simultaneously.
Normally table's of context are formatted with roman numerals. Based on the responses in the forum, only Arabic numbers are allowed. Request the ability to change the formatting of the rule numbers and restart the page numbering after the TOC.
