---
title: Choosing the columns of a report
description: "The column picker gathers several data origins, grouped under headings. At least one column is required to save the report. ## Where the offered columns come from | Origin | Content | | --- | --- | | Core attributes…"
url: "https://illizeo.com/en/centre-aide/choosing-report-columns/"
updated: "2026-09-20"
category: Core HR services / People Analytics
---

# Choosing the columns of a report

The column picker gathers several data origins, grouped under headings. At least one column is required to save the report.

## Where the offered columns come from

| Origin | Content |
| --- | --- |
| Core attributes | The core file fields: name, employee number, dates, status, assignments |
| Custom fields | Fields added by your organisation |
| Profile columns | Root sections of the employee master data, single-entry only |
| Module columns | Absences, Attendance, Payroll — present only if the module is subscribed and installed |

## A limit worth knowing

The picker **does not expose the whole employee profile**. Two data layers coexist in Illizeo, and the builder reads only the first, topped up with the root sections of the second. In practice, the following are excluded:

- **country variants** of a section;
- **multi-entry sections**, those where an employee can hold several rows.

If you are looking for a field that plainly exists on the employee record but cannot be found in the picker, one of these two reasons is almost certainly why.

## Advice

*Build a short report first — five to ten columns — check it returns the right rows, then enrich it. A forty-column report that turns out to be badly filtered takes a long time to debug.*

### *Related*