I have a cross tab where I would like to have a sub report that spans across the row groups on the left and across all column groups on the right. This is tough because I don't know how many columns will end up because it depends on my data.
Is there anyway to make a sub report span row and column groups that it is flush with the left and right borders regardless of the number of columns?
4 Answers, 1 is accepted
You can test using automatic layout options such as Docking and Anchoring - Automatic Layout (Dock and Anchor). A Panel item can be used as a container for the crosstab and sub reports.
If your layout is more complex attach some screen shots that demonstrate the exact requirement.
Regards,
Katia
Progress Telerik
Thanks for getting back to me, Katia.
I added a screenshot (This is just a mock-up of the report and how we want it to look).
It is a crosstab and on the left side of the vertical red line are the column groups with a variable number of columns depending on the data. On the right side of the vertical red line are the static columns. The area with the head 'Note', which is outlined in blue, is where I am having the problem. We want this portion to be grouped in the same row group as the item above, but we want it to span however wide the crosstab will be. We don't know how wide the crosstab will be until the user selects from parameter values and runs the report.
Is is doable to have the 'Note' section span the entire crosstab despite the number of columns that are output?
Thanks,
Phillip
The Note section demonstrated in the attached mock-up cannot be created within the same Table/CrossTab item as cells from different column groups cannot be merged.
My suggestion is to use a separate Table item to display the Note section and set its anchoring properties so it can be resized according to the width of its container. The attached report demonstrates this approach.
Another approach can be to change the width of the table that displays the Note section at runtime based on the received data. This can be achieved by adding a binding for table's properties into Bindings collection of the Table item.
Regards,
Katia
Progress Telerik