1.2Placing fields & understanding sections
The essentials in 30 seconds
- Golden rule: data → Details (one per row), column headings → Page Header, title → Report Header (1×), totals → Report Footer (1×) — drag from the Field Explorer.
- Field object vs text object: variable data versus fixed text; you can combine them (“Invoice no. ” + number field).
- Clean columns: align each field under its heading (tools + grid, not by eye) and keep Details compact.
Running mini-case — Farès structures his sales report
Farès takes over the base generated in 1.1: he drags the date, customer and amount fields into the Details section, renames the automatically created column headings in the Page Header (“Customer”, “Amount”), and places “Sales report — July” in the Report Header. He aligns each amount under its heading with the alignment tools and the grid, then reserves the Report Footer for the grand total. Switching to Preview, he finally sees clean rows instead of a mess.
Continuation of case 1.1 — Farès moves from foundations (tables) to structure (sections).
1. The golden rule: every item has its section
Designing is essentially placing fields in the right sections: you drag from the Field Explorer, and the position determines the behavior (sections govern where and how many times an item appears).
Golden rule: data (database columns) → Details (one per row); column headings (fixed text) → Page Header; report title → Report Header (once); grand totals → Report Footer (once). Farès applies it to his report: a title repeating on every row means a title mistakenly placed in Details.
2. Field objects, text objects and automatic headings
When placing a field in Details, Crystal Reports often adds a matching column heading in the Page Header (the field name) — rename it clearly (“Amount” rather than “AMT_NET”). Distinguish field objects (variable data) from text objects (fixed text: titles, labels).
You can combine fixed text and a field in the same text object (“Invoice no. ” followed by the number field). Fields and objects are handled like in page layout: select, move, align, resize.
3. Aligning for a clean report
Good practices: carefully align each Details field with its column heading (alignment tools + grid) for clean columns; keep the Details section compact (section height = row height) for a dense, readable report.
The lasting reflex: before placing an object, ask yourself “how many times must it appear?” — once (report), per page, per row (Details), per group (level 2) — and place it in the matching section. Work in Design (structure), check in Preview (real data).
The travelling title (never do this)
Moral: in Details, everything repeats — even mistakes.
🔎 Concrete example — 🔎 Concrete example — Right placement makes the table
Farès's sales report, item by item.
“Sales report — July” → Report Header (1×).
“Customer” “Amount” (headings) → Page Header.
Name, amount (data) → Details (one row per sale).
Grand total → Report Footer (1×).Reading: each frequency has its section; nothing repeats by accident.
Lesson: align each field under its heading (grid + tools), not by eye.
Section vocabulary
- Placing a field
- DRAGGING a field from the explorer to a section; its position determines its behavior (where and how many times it appears).
Simple example: Farès drags the amount field into Details: one value per sales row.
What it is not: typing a fixed value from the keyboard.
Reflex: always start from the Field Explorer.
- Golden section rule
- Data → DETAILS (one per row); column headings → PAGE Header; title → REPORT Header; totals → REPORT Footer.
Simple example: Farès's grand total reserved for the Report Footer (1×).
What it is not: stacking everything in Details.
Reflex: “how many times?” before each placement.
- Field object vs text object
- Field object: shows VARIABLE data. Text object: FIXED typed text (titles, labels); combinable in the same object.
Simple example: “Invoice no. ” (fixed) + number field in a single text object.
What it is not: two separate objects impossible to combine.
Reflex: fixed + variable together when they form one sentence.
- Automatic column heading
- Heading created in the Page Header when placing a field in Details (field name), to be renamed clearly.
Simple example: “AMT_NET” renamed “Amount” by Farès.
What it is not: a heading to retype from scratch.
Reflex: check and rename each generated heading.
In practice — In practice — Placing fields in sections
- Drag the data fields from the explorer to DETAILS (per-row repetition); rename the column headings in the Page Header.
- Place the report title in the REPORT Header (once); plan grand totals for the REPORT Footer.
- ALIGN each Details field with its heading (alignment tools + grid) for clean columns.
- Keep the DETAILS section compact; distinguish field objects (data) from text objects (fixed).
Ready-to-say script — distribute before aligning (30 s)
“My data goes into Details — one per row — my column headings into the Page Header, the title into the Report Header, the total into the Report Footer. I rename the generated headings, I align each field under its heading with the tools, and I check in Preview.”
Say in Design mode while showing each section; switch to Preview at the end.
Copy-paste template — placement grid
REPORT Header: report title (1×).
PAGE Header: column headings (repeated per page).
DETAILS: data fields (1 pass per row) — COMPACT section.
PAGE Footer: pagination (1.4). REPORT Footer: grand totals (1×).
TEST: “how many times?” → right section. CHECK: Preview.Farès's sales report
As in 1.1: date/customer/amount in Details, renamed headings in the Page Header, “Sales report — July” in the Report Header, total in the Report Footer.
Invoice with combined label
“Invoice no. ” text object + number field in the header: fixed and variable in a single object, neatly aligned.
Dense stock list
Details reduced to minimum height: compact rows for a 500-item inventory readable page after page.
Quick troubleshooting
Total repeating on every row: switch to Design, move it from Details to the Report Footer, check in Preview.
✓ Best practices
- Before each object: “how many times must it appear?” → the right section.
- Align with tools and grid, not by eye.
- Align numbers right, text left (prepares 1.3).
✗ Common pitfalls
- A title in Details: it repeats on every row.
- A total in Details: it appears on every row instead of once.
- Columns aligned by eye (draft-looking instead of professional report).
Key takeaways
- Designing = placing fields in the right sections. Golden rule: data → Details; headings → Page Header; title → Report Header; totals → Report Footer.
- Respecting “item type → section” produces a structured report; ignoring it produces inconsistency.
- Distinguish field objects (data) from text objects (fixed); they can be combined.
- Align fields with their headings, keep Details compact, name clearly: that is what makes the report readable.
48h challenge — apply tomorrow
Take your 1.1 base: move each object to its right section, rename the headings, align with tools + grid, compact Details, then compare Design vs Preview.
- I place data, headings, title and totals each in its section.
- I distinguish field objects from text objects (and combine them if needed).
- I align with tools and check the result in Preview.
Frequently asked questions
How to get clean, well-aligned columns?
Place headings (Page Header) and fields (Details) correctly, then align them vertically: same horizontal position and same width per column, with the alignment tools and grid (not by eye). Harmonize widths (enough for the content), align content by type (numbers right, text left), keep Details compact, and check in Preview that nothing overflows.
A title or total appears on every row: why and how to fix it?
Because it sits in the DETAILS section, which repeats per record. Fixes: report title → REPORT Header; column heading → PAGE Header; grand total → REPORT Footer; subtotal → group footer (level 2). Switch to Design, move the object, check in Preview.
Where should data fields go so they form the report rows?