Completed
Last Updated: 19 Jan 2023 08:31 by ADMIN
Release R1 2023
Henrique
Created on: 08 Oct 2019 08:08
Type: Bug Report
3
Sub-report does not grow to fill the entire SubReport item area
I have a report that has a sub-report inside it and it's working just fine.

The sub-report can give one or multiple lines as output for a single row in the master report.
However, when a row's height in the master report is too high (due to the output of other cells, not the sub-report), then the sub-report's output doesn't fill the gap in the master report even when I use anchoring to top and bottom.
4 comments
ADMIN
Milen | Product Manager @DX
Posted on: 19 Jan 2023 08:31

All,

Please install the latest R1 2023 where the issue is addressed.

Regards,
Milen
Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at https://learn.telerik.com/.
SwanB
Posted on: 06 Dec 2022 11:03

Todor,

 

Good job 👍,
that is so good to hear.


Looking forward to test when next Internal Build or Official Version

ADMIN
Todor
Posted on: 02 Dec 2022 11:51

Hi Svein and all,

I am happy to inform you that the problem is fixed and is currently going through our well-established procedures of code reviews and testing.

We hope to release the fix with our next Internal Build or Official Version, whichever comes first.

Regards,
Todor
Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at https://learn.telerik.com/.
SwanB
Posted on: 28 Nov 2022 08:39

We are running the most recent Reporting version 16.2.22.1109 and we are facing the exact same bug.
If the date of this ticket is correct?, this bug has been known for more than 3 years and is still not fixed.

We have invested a lot of development time into a rather complicated Report/sub reports design/setup, only to being stopped by this bug.

Would it be possible to having an interim build of version 16.2.22.1109 that fixes this nasty bug ?