1.1Creation Wizard & choosing tables
The essentials in 30 seconds
- Wizard = decisions in order: source + tables (with their links), fields to display, possible groupings, then sorts/filters — via “Create New Report with Wizard”.
- Minimum useful set: take only the needed tables (e.g. Orders + Customers, not the 40 others) — fewer tables = simpler, faster, more reliable.
- Links must not be rushed: with several tables, define the joins; the generated report is a starting point to customize (or start from a blank report once you are skilled).
Running mini-case — Farès, management controller in Algiers
Farès, management controller in Algiers, must produce the monthly sales-by-customer report for his management. He launches “Create New Report with Wizard”, connects to the database, and selects only two tables: Sales and Customers. When the wizard asks for links, he checks the join on the customer ID instead of clicking “Next” mechanically. He picks the useful fields (date, customer, amount), adds a grouping by customer, and gets a working base report that he will refine later (formatting, totals, pagination).
This same case returns in the lesson, the diagram, the script and the 48h challenge — and continues in 1.2, 1.3 and 1.4.
1. The wizard guides the founding decisions
The simplest way to create a first report is the Report Creation Wizard (Report Wizard): “Create New Report with Wizard”. It chains decisions in the right order: source and tables (with their links if several), fields to display, possible groupings, then sorts/filters/template.
At the end, it generates a working base report — a clean starting point you refine afterwards. Farès uses it for his sales report: he answers the right questions (which data? which fields? which grouping?) instead of improvising. You can add/remove tables later via the Database Expert.
2. Choosing the right tables (the minimum useful set)
Choosing tables is structural: take only the needed tables — for an order list with the customer name, Orders + Customers, not the 40 other tables. Start from the need: list the wanted information, then the tables that hold it (plus the indispensable linking tables).
With several tables, the wizard asks you to define the links (joins) — a step not to be rushed: correct links = an accurate report; rushed links = duplicates, missing rows, inflated totals. Each superfluous join is a potential source of wrong results.
3. A starting point, not an end result
The generated report is a starting point: you customize it afterwards (formatting, formulas, sections — sections 1.2 to 1.4). Taking it for a finished product means distributing a raw document. Alternative: the blank report, built entirely by hand — useful for unusual reports or once you are skilled.
In practice, many lay the foundations with the wizard (source, tables, links, fields, group) then customize manually. Laying healthy data foundations is the first design skill.
🔎 Concrete example — 🔎 Concrete example — Taking the minimum of tables
Farès's sales list, without loading the whole database.
Need: sales of the month + customer name.
❌ Loading the 40 tables of the database: slow, parasitic joins, risky totals.
✅ Sales + Customers, linked on the customer ID. Simpler, faster, more reliable.Reading: each table answers a wanted piece of information; nothing is taken “just in case”.
Lesson: start from the need (which information → which tables), check the link before generating.
Section vocabulary
- Report Creation Wizard
- Guides report creation step by step: source/tables → fields → groupings → sorts/filters/template; the recommended method to get started.
Simple example: Farès launches “Create New Report with Wizard” for his sales report.
What it is not: a blank report built entirely by hand.
Reflex: beginner or standard report = wizard first.
- Table selection
- Selecting ONLY the tables needed for the report, not the whole database.
Simple example: Sales + Customers for Farès's list, not the 40 other tables.
What it is not: loading the whole database “just in case”.
Reflex: one wanted piece of information = one table; the rest stays out.
- Links (joins)
- Relationships between tables on a common field, defined in the wizard; they determine the accuracy of the report.
Simple example: The Sales ↔ Customers link on the customer ID, checked by Farès.
What it is not: a simple display filter.
Reflex: several tables = check each link before generating.
- Base report
- The working report generated by the wizard: a clean STARTING POINT to customize (formatting, totals, pagination).
Simple example: Farès's raw report before sections 1.2 to 1.4.
What it is not: a finished document ready to distribute.
Reflex: generate, then refine by hand.
In practice — In practice — Creating a report with the wizard
- Launch “Create New Report with Wizard”; choose the data source.
- Select ONLY the needed tables (e.g. Sales + Customers) and define their LINKS if several.
- Choose the FIELDS to display (Details-section columns), then optionally a GROUPING (by customer, by month…).
- Finish the wizard: you get a working base report — a starting point to customize afterwards.
Ready-to-say script — launching your first report (30 s)
“I launch Create New Report with Wizard, I choose my source, I take only the useful tables — Sales and Customers — I check the link on the customer ID, I choose my fields and a grouping by customer. I get a clean base that I will refine.”
Say while walking through the wizard screen by screen; stress checking the link.
Copy-paste template — wizard check-list
NEED: which information must appear?
TABLES: only those holding it (+ indispensable linking tables).
LINKS: each table linked by a common field — checked.
FIELDS: useful columns → Details. GROUP: by customer / by month if needed.
RESULT: base report = STARTING POINT, to customize (1.2 → 1.4).Monthly sales report
Like Farès in Algiers: Sales + Customers, link on the customer ID, date/customer/amount fields, grouping by customer — the report requested by management.
Stock list
Items + Movements linked on the item reference: quantities and labels are enough, no need for the accounting tables.
Customer statement
Customers + Invoices + Payments: three tables linked in a chain, fields filtered later (level 2) — set the links right in the wizard.
Deliberate blank report
Unusual off-template report: start from a Blank Report and build everything by hand — reserved for cases where the wizard forces a wrong structure.
✓ Best practices
- Start from the need: list the wanted information, then the tables holding it.
- Take only what is needed (plus the indispensable linking tables).
- Use the wizard for the foundations, then customize by hand.
✗ Common pitfalls
- Loading the whole database “just in case” (slow, parasitic joins, wrong totals).
- Rushing the links between tables (wrong report with no error message).
- Taking the wizard report for a finished product (it is still raw).
Key takeaways
- The WIZARD chains source/tables → fields → groupings → sorts/filters: the right questions in the right order.
- TABLE SELECTION = a structural decision: take only what is needed (less = simpler, faster, more reliable).
- With several tables, define the LINKS (joins) — a step not to be rushed.
- The wizard report is a STARTING POINT (customize afterwards). Alternative: the BLANK report.
48h challenge — apply tomorrow
Launch the wizard on a real need: list 3 wanted pieces of information, keep 2 tables maximum, check their link, choose the fields and generate the base. Note what remains to be refined.
- I launch a report with the wizard in the right order (tables → fields → groups).
- I take only the needed tables and I check their links.
- I treat the generated report as a starting point to customize.
Frequently asked questions
Should I use the wizard or start from a blank report?
Both are valid. The wizard guides the founding decisions (source, tables, links, fields, groupings) in the right order, avoids omissions and quickly produces a clean base — ideal for beginners and standard reports. The blank report starts from an empty report and leaves everything to be built by hand: total control, useful for unusual reports or once you are skilled. In practice, lay the foundations with the wizard then customize manually.
How to choose the right tables and why limit their number?
Start from the need: which information must appear → which tables hold it → take only those (plus the needed links). Check that they connect through a common field. Limiting the number makes the report simpler (fewer links), faster (light query) and above all more reliable: each superfluous join risks duplicates that inflate totals or missing rows.
Why limit the number of tables in a report?