My report consists of a Report Header and a Detail section. Their design-time height is totally less than 20mm. There are no PageBreaks or GroupPageBreaks and all KeepTogether properties are False. In Print Preview, the Detail section starts from the second page when the PaperSize Height is 88mm or less. This is not expected as there is sufficient space left after the Report Header. The Detail section starts rendering from the first page only when the paper height is more than 88mm, which is the expected behavior.
See the forum post Report Header and Detail Section does not print together for the report definition that allows reproducing the issue.
The mark for the ToggleVisibility action is displayed in the center If the The position is adjustable or fixed in top it will be better, Please consider this now its not looking good.
Please find the attached image
Standalone Report Designer is not localized when the trdp file is opened. The localization only takes effect when the executable file is started first and then the report is opened.
Reproducible in R2 2020 14.1.20.513
For the new Swiss paiment system, we need to add a QR Code with a logo inside it. The logo must be centered and be 7x7 mm.
Currently, there is no possibility to do it with Telerik Reporting, so please add it.
Current Behavior
1. Open the Standalone Report Designer.
2. Navigate to the Open Menu.
3. Select the Computer Tab.
4. Observe the available list of folders under the Computer Menu.
5. Navigate to the Options Menu.
6. Change the Default Working Directory.
7. Navigate to the Open Menu.
8. Observe the Available Folder and the directory will not be listed.
9. Select the Browse Button.
10. Observe the open folder is not the expected Default Working Directory from Step 6.
Expected Behavior
It would be nice to remove the previous folder from the Standalone Report Designer Open Menu.
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?
I have designed a report that includes an embedded SubReport. When I render it to PDF, it looks correct. When I render it to CSV, there are two issues that are probably related:
- The heading row columns should contain the main report's detail row textbox names followed by the SubReport 's detail row textbox names. However, the SubReport 's detail textbox names are repeated a few times instead of just included once.
- In the situation where there is no detail row in the SubReport, a CRLF is missing at the end of the main report's detail data. The next main report detail data appears on the same row, following the previous main report's last detail column -- it should begin on the next line.
I understand that CSV Rendering is not recommend for hierarchical output as described in the CSV Design Considerations. However, I am using the Hide the SubReport if no Values to not display the SubReport when there is not data. The hidden SubReport implementation can be seen in the below binding expression.
<Bindings>
<Binding Expression="=Count(Fields.AP_OPN_CHK_VCH_NO_C)>0" Path="Parent.Parent.Parent.Visible"/>
</Bindings>
Using the above approach, the master report is missing a CRLF when the detail data is not visible. The record shows it appended to the previous record.
I started working with Support on this issue and have discovered that it might be a bug. As a result, I am also attaching their sample to help replicate the issue. For the pdf and csv output see the first attachment in the original ticket.
I am suggesting a global 'this.value' option for conditional formatting. This approach would allow quick use of the fields value to be the basis of the condition. In reports that use complex and sometimes lengthy calculations, this is would be a huge timesaver. This feature would also have to work with your current 'cut and paste' rule feature.
If I had to create individual rules for each box on a page, or a series of rules for each box to do multiple colors it would be a very unproductive use of time for me.
Putting my one project in perspective, if I had to do it with rules.
Right now, I have over 300 fields with 2 rules each, which is 600 rules to write and that is only about 75% of what I need on a single page of the report. This is a serious time burn activity just to get something like a conditional formatting to work on the value of the field. The rule approach might be good if the solution has less than 10 fields, but to have the shear numbers I do, I do not think it rule creation for each field is a viable solution. Another solution proposed was to create additional calculated columns. The problem with this is that the data source already has 100+ columns and I would hate to add any more fields (at least 100+ more), due to performance considerations.
I love the Telerik reporting solution do to the instant flexibility in my apps, but the conditional formatting is lacking especially if you use it for large analysis reports with comparisons that the client (and myself) would like coloring of the text to 'see' things easier.
Telerik: See ticket 1462207 as reference