Table of Contents

JSON export

The JSON export produces a structured .json representation of the rendered report. It is provided by the core combit.ListLabel32.CrossPlatform package and selected with LlExportTarget.Json.

JSON is intended for machine-to-machine consumption, for example by web services that need to post-process report content rather than display the rendered output directly.

Supported export options

All options are set on ExportConfiguration.ExportOptions using the LlExportOption keys listed below. Values are always strings.

ExportInfinitePage

Renders the report onto a single, very tall page instead of breaking it according to the project's page size. The exporter also skips font measurement when this option is enabled, which can significantly reduce export time for purely data-driven reports.

Value Meaning
"0" Default. Page breaks follow the project's page size. Font metrics are evaluated.
"1" The report is rendered as a single continuous page. Font measurement is skipped.
Warning

The infinite page is internally limited to 7200 pages worth of content.

JsonAutoDetectDataType

Writes table cell values as typed JSON values instead of display strings. The type is taken from the expression type of the cell's content formula, not from the rendered text, so a string expression that happens to look like a number stays a JSON string.

Value Meaning
"0" Every cell value is written as a JSON string, using the formatted display text including any output formatter.
"1" Default. Numeric contents become JSON numbers, boolean contents (including checkbox fields) become JSON booleans, and dates become round-trippable ISO 8601 strings.

Typed values are taken from the evaluated value itself, so they are lossless and deliberately bypass the field's output formatter. Values whose type cannot be determined — most notably NULL — fall back to the formatted string.

Restrictions

  • The JSON output is intended for downstream tooling. The schema is not a stable public contract; treat it as the structural representation produced by the current renderer.
  • Visual fidelity (anti-aliased fonts, vector shapes) is not part of the JSON export.
  • With JsonAutoDetectDataType enabled, an output formatter configured on a table field has no effect on the exported value: typed values always carry the raw data. Disable the option when the formatted text is required.
  • JSON has no native date type. Dates are therefore still exported as strings, just in a round-trippable format rather than the localized display text.