Skip to content

Compose and save an export (CSV / Excel)

The Data export tab takes analytics data out into a spreadsheet — in the page’s own words: “Compose the report: date range, resolution, metric columns and scope. One row = one period + one plant.” A finished set-up can be kept as a saved export, so the monthly routine never has to be re-clicked.

  • Permission: analytics:view is enough to download; creating a saved export needs the management right — the UI explains why: “Saved exports are shared tools of the organisation — saving them needs the analytics management right. You can load and download them without it.”
  • Site: “Pick a site in the header to export — the scope of analytics is always a single site.”
  1. Open the “Export” tab from the analytics tab bar. It starts with the selected period and the ones preceding it — everything can be changed.
  2. Set the frame: “Resolution” (day / week / month / year), the date range and the “Scope” (the whole site or one plant).
  3. Pick the columns. The “Operating-mode columns” give the recorded time per operating mode in hours — “The columns come from what actually has data in the period.” From the “Metric columns” list you can add up to 8 metrics; each one also gets a sample-count column, because “the number alone would not say how many measurements it came from.” The “Break down by shift” toggle adds one row per shift alongside the aggregate row — the per-shift value does not double-count the aggregate.
  4. Check the “Preview” table. “The preview and the download are built from the same core — what you see here is what goes into the file.” The line beneath states the included periods and the row count.
  5. Download: “Download CSV” or “Download Excel”.
  6. (With the management right) save it: in the “Save as a saved export” box give it a name and pick the range kind — “Rolling window: the last {n} periods, always up to today” or “Fixed span”. As the help text puts it: “The rolling window exists so you do not have to put the same report together every month: the saved export follows the day you load it. A fixed span preserves a closed period unchanged.”

The downloaded file carries one period + one plant per row with the chosen columns; the saved export appears in the “Saved exports” list, and the “Load {name}” button restores the whole set-up in one click.

What you see Why What to do
“There is no data in the selected range. Analytics computes from recorded shift logs — if you have just started, records must come first.” No diary was recorded for the range. Pick a range that already has data — or record first.
“The range is capped at {n} periods — older periods were left out.” The range is too long for the chosen resolution. “Narrow the range, or pick a coarser resolution.” (monthly instead of daily, say).
“At most {n} metric columns.” More metrics selected than the cap. Split it into two exports — both can be kept as separate saved exports.
“This metric is not selectable — the meaning of the number is not set —, so it gets no column.” The field’s meaning assignment is missing. The meaning is set in the datapoint settings (needs the management right).
“A saved export with this name already exists in this scope.” Name clash among saved exports. “Pick another name, or update the existing one” via “Update with the current set-up”.
  • A metric referencing the previous period (a prev. formula, say) “has no value in the first period of the range” — that is a definition, not a bug.
  • A saved export keeps the whole set-up: “resolution, range, metric columns, scope, format and the operating-mode columns.” Update it with “Update with the current set-up”; concurrent editing is guarded by CAS (“Someone else has changed this saved export in the meantime…”).
  • The dashboard leads here too: the overview’s download button opens the Export tab pre-filled with the page’s period — refine from there.

Last updated: