Data (QR Code)

Lede. Reads a column value from the current record and forwards it as the QR-code payload.

Group: Data · Available in: QR Code Placeholder · Central node: No

Purpose

• Encode a per-record URL into a scannable QR code.
• Encode a SKU or order number for warehouse picking.
• Encode a contact card (vCard) string assembled from several columns.

Where to find it

Add Node ▸ Data ▸ Data

This is the same node class as Data Text, exposed under the Data category of QR-code placeholder workspaces. The QR code is rendered by InDesign from the text value this node emits.

How it works

Identical behaviour to Data Text: pick a column, optionally chain upstream input and apply a Formatter. The emitted text becomes the QR code’s payload.

Sockets

Settings

Same as Data Text.

Example (end-to-end)

Scenario. A product label that includes a QR code linking to the product page.

Wiring.

[Static Text: "https://example.com/p/"] → [Data Text: SKU] → [Placeholder.Content]

In a QR-code placeholder the chain looks identical to a text placeholder; the central node decides to render the result as a QR image.

Empty / error behaviour

Same as Data Text. The placeholder’s Error Action socket handles empty / invalid payloads.

Limitations

• No Formatter ordering specific to QR codes – formatters operate on the text payload, not on the QR rendering.
• QR-specific rendering options (error correction level, size, …) live on the placeholder, not on this node.

Common pitfalls

• The QR code won’t scan. Verify the emitted text in the preview is the URL/value you expect; the QR is only as good as the input text.

Related nodes

• Data Text – same behaviour; this is the QR-workspace face.
• Style Object – applies an object style to the QR frame.
• Placeholder – QR Code – the consumer.

Screenshots

📷 Screenshot [NEU]: Data node panel inside a QR-code placeholder workspace