Export formats and filters

Purpose

This topic explains how Actualog chooses export scope, how applied filters are recorded, and when to use JSON or CSV.

Where results appear

The result page is determined by the page that queued the export:

  • Product Overview and Sales Catalog exports appear under Company Workspace -> Data Integration -> Exports.
  • Product Stewardship and Expert-page exports appear under Expert -> Exports.
  • Platform administrator exports appear under Admin -> Integrations -> Exports.

Completion notifications use the same routing. Download export returns the file directly, while Open exports opens the correct export list for the export's owner scope.

Export scope

Most export-enabled lists support three practical scopes:

  • Selected rows: only the rows you selected after turning on Select mode.
  • Current page: the visible page of results after filters and sorting are applied.
  • All matching filters: every record that matches the current applied filters, including records on other pages.

Some lists also support all matching filters except exclusions, where you select all filtered records and then remove a few rows before queueing.

Filters in the file

When you export all matching filters, the JSON file includes a filters section. It records the applied list search text, category or community scope, type flags, sort order, and other supported filter values. This helps reviewers understand why a record was included in the file.

Only applied filters are used. If the page says filters are dirty or not applied yet, apply filters before exporting all matching results.

Expert list exports record the filters used by that list. Examples include category workflow and community filters, attribute group and library-only filters, company profile quality filters, measure category-use filters, sort, order, and excluded visible rows when you remove rows from an all-filtered selection.

JSON

Use JSON when you need structured data with nested details, such as product attributes grouped by category template, category template snapshots, measure definitions, attribute metadata, community links, and related references.

Product JSON is grouped by category. Communities and facets are written once per category, followed by clean product entries with names, identifiers, brand/company links, images, and grouped attributes.

Category JSON uses category template snapshots. Attribute entries use attributeType and omit retired recommendation-only legacy fields.

Expert list JSON uses the same envelope and then writes list-specific items:

  • Attributes include name, type, library flag, group, measure or unit summary, category usage, and type-specific definition.
  • Attribute groups include names, linked attributes, and category usage.
  • Companies include list-safe profile and verification fields, community links, and facet links. Secrets, API keys, billing internals, and private integration credentials are not exported.
  • Measures include names, category-use flag, QUDT or dimension metadata where available, and units with symbols, coefficients, and base-unit information.

CSV

Use CSV when you need a spreadsheet-friendly report or a lightweight integration handoff.

CSV is flat. It includes practical list columns such as identifiers, names, status, category, company or brand context, timestamps, flags, and summary counts. CSV does not try to represent deeply nested product attributes or category templates as a full round-trip file.

File names

Download names use readable UTC timestamps, for example:

actualog-products-product-overview-export-2026-07-13-14-05-22.json
actualog-categories-expert-categories-export-2026-07-13-14-05-22.csv
actualog-attributes-expert-attributes-export-2026-07-13-14-05-22.json
actualog-measures-expert-measures-export-2026-07-13-14-05-22.csv

Common mistakes

Do not assume current page means all filtered results. Current page exports only what is visible on that page. Use all matching filters when the file must include every matching record.

Do not look for Product Stewardship or Expert-page files under company exports. Those results are Expert workspace exports.