Grouping needs a databand and Footers not visible

Stimulsoft Reports.WPF discussion
Post Reply
mvijs
Posts: 2
Joined: Thu Feb 18, 2010 7:36 am
Location: The netherlands

Grouping needs a databand and Footers not visible

Post by mvijs »

We are evaluating the reports.wpf version and ran into some questions.
First our datasource is a xml-file which looks like this:

1
Order 1
...

1
1
Product 1
...

1
1
Calculation 1
...



2
1
Product 2
...

1
2
Calculation 1
...




2
Order 2
...

3
2
Product 3
...

2
3
Calculation 2
...


3
3
Calculation 3
...




When I set the Datasource, I noticed that there where automaticaly added some ID-fields for relation purposes.
I am using these ID-fields for groupings.

Now I am trying to create a report which will create for each Order a page.
So this is what I created:

Attempt 1:
[GroupHeaderBand1 -> Cond: Order.Autogenerated_Order_id] --> pagebreak-options: newPagebefore, skipfirst
[GroupHeaderBand2 -> Cond: Product.Autogenerated_product_id]
[GroupHeaderBand3 -> Cond: Calculation.CalculationID]
[Databand 1 : Calculation]
[GroupFooterBand3]
[GroupFooterBand2]
[GroupFooterBand1]

Result:
Now a report is generated with 1 order, 1 product, and all the calculations
All groupfooters are visible.


Attempt 2:
I added a Product Databand like a master-detail
[GroupHeaderBand1 -> Cond: Order.Autogenerated_Order_id] --> pagebreak-options: newPagebefore, skipfirst
[GroupHeaderBand2 -> Cond: Product.Autogenerated_product_id]
[Databand 1 : Product]
[GroupHeaderBand3 -> Cond: Calculation.CalculationID]
[Databand 2 : Calculation]
[GroupFooterBand3]
[GroupFooterBand2]
[GroupFooterBand1]

Result:
Now a report is generated with 1 order, All products with their calculations
Only GroupFooterBand3 is visible after each Calculation.

Attempt 3:
I added a Order Databand like a master-detail
[GroupHeaderBand1 -> Cond: Order.Autogenerated_Order_id] --> pagebreak-options: newPagebefore, skipfirst
[Databand 1 : Order]
[GroupHeaderBand2 -> Cond: Product.Autogenerated_product_id]
[Databand 2 : Product]
[GroupHeaderBand3 -> Cond: Calculation.CalculationID]
[Databand 3 : Calculation]
[GroupFooterBand3]
[GroupFooterBand2]
[GroupFooterBand1]

Result:
Now the report is generated with 2 orders with their product(s) and their calculation(s).
Only GroupFooterBand3 is visible after each Calculation.

Questions:
1. Is it normal that there must be a databand on each grouping level???
2. Why are the GroupFooters of Band1 and Band2 not visible??
Edward
Posts: 2913
Joined: Fri Jun 09, 2006 4:02 am

Grouping needs a databand and Footers not visible

Post by Edward »

Hi

Could you please send data and report template to support[at]stimulsoft.com for analysis?

Also please see 'Business Objects' sample application, which shows the way business objects will be registered in the Dictionary.

If databands are connected with each other with a relation, that the correct order will be the following:

[GroupHeaderBand1 -> Cond: Order.Autogenerated_Order_id] --> pagebreak-options: newPagebefore, skipfirst
[GroupHeaderBand2 -> Cond: Product.Autogenerated_product_id]
[Databand 1 : Product]
[GroupFooterBand2]
[GroupFooterBand1]
[GroupHeaderBand3 -> Cond: Calculation.CalculationID]
[Databand 2 : Calculation][HERE RELATION WITH DATABAND1 ALLOWS TO HAVE 'DETAIL GROUPPING']
[GroupFooterBand3]

Thank you.
mvijs
Posts: 2
Joined: Thu Feb 18, 2010 7:36 am
Location: The netherlands

Grouping needs a databand and Footers not visible

Post by mvijs »

Hi Edward,

With your suggestion, I managed to get the output we wanted.
This is how the bands look like:

[GroupHeaderBand1 -> Cond: Order.Autogenerated_Order_id] --> pagebreak-options: newPagebefore, skipfirst
[Databand 1 : Order]
[GroupFooterBand1]
[GroupHeaderBand2 -> Cond: Product.Autogenerated_product_id]
[Databand 2 : Product][HERE RELATION WITH DATABAND1 ALLOWS TO HAVE 'DETAIL GROUPPING']
[GroupFooterBand2]
[GroupHeaderBand3 -> Cond: Calculation.CalculationID][HERE RELATION WITH DATABAND2 ALLOWS TO HAVE 'DETAIL GROUPPING']
[Databand 3 : Calculation]
[GroupFooterBand3]

For me this is not very intuitive and I think our customers feel the same.
Is it the way we provide the data that the reporttemplate has to look like this??
If so, what datasource should we use to setup a more intuitive way of the report??
like:

[GroupHeaderBand1 -> Cond: Order.Autogenerated_Order_id] --> pagebreak-options: newPagebefore, skipfirst
[GroupHeaderBand2 -> Cond: Product.Autogenerated_product_id]
[GroupHeaderBand3 -> Cond: Calculation.CalculationID]
[Databand 3 : Calculation]
[GroupFooterBand3]
[GroupFooterBand2]
[GroupFooterBand1]

At the moment we are using Crystal Reports to produce reports from our software.
One big shortcoming is that the costumers cannot change the layout (fieldposition, font, etc) of the report.
Thats why we are looking for a new reportingtool. Your reporttool looks promissing, but has to be intuitive.
Andrew
Posts: 4108
Joined: Fri Jun 09, 2006 3:58 am

Grouping needs a databand and Footers not visible

Post by Andrew »

Hello,

You may have such a structure.
But in this case you may have all datasources which are united into one datasource (as in Crystal).

In our previous post we described how to do this if data are represented as a separate datasource.

Thank you.
Post Reply