Report Outline Problem
I am using RB7.03. I have a few report with 3 groups, Group1=Sales Region,
Group2=Sales Area, Group3(Start new page)=Customer. I have enable the
outlet settings, and select create nodes for ppReport,ppGroup1,ppGroup2 and
ppGroup3, and select not to create page nodes. When I preview the report,
the report outline is shown like this:-
Main
-- customer1
-- region1
-- area1
-- customer2
-- customer3
-- customer4
-- area2
-- customer5
-- region2
-- area3
-- customer6
-- customer7
Customer1 is actually in area 1 in region1, but why it is shown immediately
after the Main section? Thank you.
Group2=Sales Area, Group3(Start new page)=Customer. I have enable the
outlet settings, and select create nodes for ppReport,ppGroup1,ppGroup2 and
ppGroup3, and select not to create page nodes. When I preview the report,
the report outline is shown like this:-
Main
-- customer1
-- region1
-- area1
-- customer2
-- customer3
-- customer4
-- area2
-- customer5
-- region2
-- area3
-- customer6
-- customer7
Customer1 is actually in area 1 in region1, but why it is shown immediately
after the Main section? Thank you.
This discussion has been closed.
Comments
I am unable to recreate this issue on my machine. Please send a small
example demonstrating this behavior to support@digital-metaphors.com and
I'll find a solution for you.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Funny, I had this problem in R14.08 that a customer just reported.
Turns out that if you have group headers that are hidden, or not
printed, more specifically, then this situation occurs. By showing the
group headers, even with nothing in them but the tiniest bit of white
space, the outline sorts itself out and everything is good. Visible but
height=0 was not sufficient to correct the problem.
Also of note to the original poster, the elements were actually not
always appearing under the correct subheadings either, aside from the
rogue element appearing at the top of the list.
Not sure if anyone cares, 10 years on now, but hey, maybe this will save
someone the hour or two I just spent trying to sort it out.
Andrew Simard.