2.1Sorting & grouping (groups)
The essentials in 30 seconds
- Sort = order, group = structure: sorting orders rows, grouping creates blocks with header and footer — grouping includes sorting, not the other way round.
- Group Expert = field + order: you pick the grouping field, Crystal inserts the Group Header/Footer sections — the header names, the footer will total.
- Nest in order: Region > Customer > Orders, from broadest to finest — 2-3 levels are enough.
Running mini-case — Farès and the unreadable sales report
Farès, management controller in Algiers, receives a raw list of 800 orders every month in the random order of the database: unusable for management. He starts by sorting (Record Sort, by date), then inserts a group per customer via the Group Expert: each customer gets its own block with its name in the header. He then adds a second level — a Region group above the Customer group — and sorts orders by date within each customer. The flat list becomes a Region > Customer > Orders hierarchy. This “Farès sales report” returns in 2.2 (subtotal per customer and per region), 2.3 (filtering on the current year), 2.4 (year and region parameters) and 2.5 (summary version for management).
Level 2 thread: Farès's sales report runs through the course, the diagram, the script and the 48h challenge — and continues in 2.2, 2.3, 2.4 and 2.5.
1. Sort, then group
Sorting orders records on one or more fields (ascending date, descending amount, alphabetical name), via the Record Sort Expert: you pick the field(s) and the direction. A sorted report is immediately more readable than a list in the random order of the database. Grouping goes further: it ORGANIZES records into groups based on a field value (by customer, by region, by month). Crystal Reports then creates, for each group, a Group Header section and a Group Footer section around the group's detail rows. Farès first groups by customer: all orders of the same customer end up together, named in the header.
2. How to group (Group Expert)
Use the Group Expert (Insert Group / Group Expert): pick the grouping field (e.g. the customer) and the group order (ascending, descending). Crystal Reports inserts the group sections and automatically sorts records on that field — grouping means sorting + structuring. You can create several levels of nested groups: group by region, then within each region by customer — a hierarchy (Region > Customer > Orders). The group order defines the hierarchy: the outer group first (Region before Customer). Farès checks the order in the Group Expert before confirming.
3. What grouping unlocks
The Group Header usually shows the group name (“Customer: Haddad”); the Group Footer hosts the subtotals (section 2.2). You can also sort records within each group (by date, by amount) on top of the grouping sort. Method point: distinguish sorting (ordering rows) from grouping (organizing into blocks with headers, footers and subtotals). Grouping is a core reporting concept: it turns a flat list into an organized, hierarchical report ready for totals. With groups in place, Farès will add totals and subtotals in 2.2.
🔎 Concrete example — 🔎 Hands-on example — Grouping by customer
Farès's sales report, from flat list to logical blocks:
Group Expert → group by Customer.
Group header: “Customer: Haddad”.
Details: his orders (sorted by date).
Group footer: customer total (see 2.2).Reading: each customer forms a named block, its orders are sorted, the footer awaits the subtotal.
Lesson: for a hierarchy, place the outer group (Region) before the inner group (Customer).
Section vocabulary
- Record sorting
- Ordering rows on one or more fields (ascending date, descending amount) via the Sort Expert (Record Sort).
Simple example: Farès sorts his 800 orders by ascending date.
What it is not: grouping into blocks with headers and footers.
Reflex: list to read = sort first.
- Grouping (group)
- Organizing records into BLOCKS based on a field value (by customer, region, month), with Group Header and Footer sections.
Simple example: Farès groups his orders by customer, then by region.
What it is not: a simple row order with no structure.
Reflex: blocks + subtotals wanted = group.
- Group Header / Footer
- Sections created by grouping: the Header shows the group name, the Footer holds its subtotals (2.2).
Simple example: “Customer: Haddad” in the header, the customer total in the footer.
What it is not: the report page header and footer.
Reflex: name at the top, total at the bottom.
- Nested groups
- Several nested group levels (Region > Customer > Orders); the order defines the hierarchy, outermost first.
Simple example: Farès places Region above Customer in the Group Expert.
What it is not: several independent sorts with no hierarchy.
Reflex: broadest first, limit to 2-3 levels.
In practice — Hands-on — Sort and group
- Sort records (Sort Expert) on a relevant field (date, amount, name) in the wanted direction.
- Insert a GROUP (Group Expert) on a field (by customer, by month): check that Crystal creates the Group Header/Footer sections.
- Show the group name in the Group Header (“Customer: …”); reserve the Group Footer for subtotals (2.2).
- Create NESTED groups (Region > Customer) and sort records WITHIN each group (by date/amount).
Ready-to-say script — explaining grouping to management (30 s)
“Our sales report is no longer a list of 800 rows: it is grouped by region then by customer, each block is named and sorted by date. At the foot of each block we will put the subtotal — that is the next step. Same data, but finally readable: you can see each customer, each region, without searching.”
Say while showing Farès's raw list, then the grouped report with one customer block open.
Copy-paste template — grouping plan
[Level 1] Outer group: {Commandes.Region} (ascending)
G1 header: “Region: ” + {Commandes.Region}
[Level 2] Inner group: {Commandes.Client} (ascending)
G2 header: “Customer: ” + {Commandes.Client}
Details: {Commandes.DateCommande}, {Commandes.Montant} (sorted by date)
G2 footer: customer subtotal (see 2.2)
G1 footer: region subtotal (see 2.2)Sales by month
Farès groups orders by month: each month forms a named block, ready for the monthly subtotal.
Customers by wilaya
Region > Customer hierarchy: Farès puts the region in the outer group for the summary by area.
Products by category
Catalogue grouped by category: the header names the category, details list products sorted by name.
Too many levels
Four nested levels make the report confusing: Farès goes back down to 2 levels and sorts the detail.
✓ Best practices
- Group from broadest to finest (Region before Customer).
- Sort rows within each group (by date/amount) for readability.
- Limit nesting to 2-3 levels (beyond that, the report gets confusing).
✗ Common pitfalls
- Confusing sorting (ordering) with grouping (structuring + subtotals).
- A wrong group order that flips the hierarchy.
- Too many nested levels (confusing, very long report).
Key takeaways
- SORT = order rows; GROUPING = organize into blocks (by customer, month…), creating Group Header and Footer.
- The Group Header shows the group name; the Footer holds SUBTOTALS (2.2).
- NESTED groups possible (hierarchy) — order matters (outer group first).
- Grouping is core: it turns a flat list into a usable report.
48h challenge — apply tomorrow
Take a real flat report (Farès's or yours): sort it on a relevant field, add a group via the Group Expert with the name in the header, then try a 2-level hierarchy (outermost first).
- I can sort records (field + direction) via the Sort Expert.
- I can create a group (Group Expert) with a named header and a reserved footer.
- I can nest 2 levels in the right order (outermost first).
Frequently asked questions
What is the difference between sorting and grouping, and when to use each?
Sorting ORDERS rows (by date, amount, name): they stay one continuous list, in a logical order — for a readable list with no blocks or subtotals. Grouping ORGANIZES them into groups on a field (by customer, region), creating a Header section (group name) and Footer (subtotals) around the details — to structure into categories and compute subtotals. Grouping includes a sort (on the group field) but adds structure. Use sorting alone for a simple list; grouping as soon as you want blocks or subtotals; combine them (group by customer, sort rows by date within each group).
How to build a hierarchy with nested groups?
Insert several groups; their order defines the hierarchy (the first = outer level). For “Region > Customer”: group 1 = Region, group 2 = Customer (nested inside each region). Crystal Reports creates Group header 1 (Region), Group header 2 (Customer), Details (orders), Group footer 2 (customer total), Group footer 1 (region total), Report Footer (grand total) — a pyramid of subtotals. Follow a logical hierarchy (Region > Customer, not the reverse), limit to 2-3 levels, manage pagination (new page per group if needed), and put a subtotal in each Group Footer.
What does grouping create around detail rows?