Articles in this section

"The Export Does Not Contain All Rows": Limits and Filter Behaviour of the Exports

Published:
Updated:

Module: All modules with table views

Audience: All users, support

Required permission: the page's respective .view permission

The symptom

A CSV, Excel or PDF export contains fewer rows than expected - records that are visible (or at least present) in the application are missing from the file.

Checklist (most frequent cause first)

#CheckDetails
1Export dialog answered correctly?The vehicle and driver overviews ask, when filtering is active: "Welche Daten sollen exportiert werden?" (Which data should be exported?) - "Gefilterte Ansicht" (Filtered view) exports only the visible rows, "Alle Daten" (All data) exports the complete inventory (article 118).
2Filter area of the page active?Belege (Receipts) (vehicle / from / to) and the damage overview (from / to / status) export exactly the rows that match the filter area. Use "Zurücksetzen" (Reset) to clear the filters and export again.
3Column filter or search field active?In the receipt overview, column filters also affect the export. In the damage overview and the logs, by contrast, they do not - there the export ignores column filters and the search field (see below).
4Logs: upper limit reached?The log export is limited to the 50,000 most recent entries - older ones are always missing (see below).
5Paging?Never the cause: exports always cover all pages of the table, not just the displayed page.

Special case logs: fixed at the 50,000 most recent entries

The CSV/PDF export of the Protokolle (Logs) (/applications/protokolle/overview) always exports the 50,000 most recent entries (by timestamp, descending) - regardless of which column filters or search terms are set in the table. This means:

  • With more than 50,000 entries, the oldest are missing - even if you have just filtered on an older type or period in the table.
  • Therefore filter after the export in Excel (the export contains all columns), or research older individual cases directly in the table - there filters and sorting are applied server-side to the entire inventory.
  • Also keep the retention in mind: logs are cleaned up after 365 days by default (article 16).

Behaviour per overview (quick reference)

PageWhat the export contains
Vehicles / driversdepending on the dialog: "Gefilterte Ansicht" (Filtered view) or "Alle Daten" (All data)
Receiptsthe current filtered view (filter area + column filters), all pages
Damage overview / damage lists of the recordsall rows per the filter area (from/to/status), all pages - column filters/search do not count
Analysesall calculated rows of the analysis with their set analysis filters
Logsthe 50,000 most recent entries, without regard to the table filters

Other overviews without a documented particularity export the currently filtered table across all pages; a further row limit like the one for the logs does not exist in FMWeb 10.4.0.

Tip: narrow down the period instead of a maximum export

For billing and reporting purposes, export in a targeted way: first set the filter area (e.g. one vehicle and one billing month in the receipts, status "Offen" (Open) in the damage), then export. This keeps the files small and avoids discussions about which rows are "missing".

Related articles

AH
Written by Alexander Hagemann
Updated:
Access denied
Access denied