For the complete documentation index, see llms.txt. This page is also available as Markdown.

Unique ID Chip

Unique ID Chip

Unique ID Chip

Display Notion Unique ID values (for example RST1) as a compact monospace Unique ID Chip on Details instead of plain body text.

What changed A new view component, Unique ID Chip, is preferred for Notion unique_id properties. It renders the ID as a clear chip so ticket/restaurant/request identifiers are easy to scan and copy mentally.


What you get

Capability
Maker setup
End-user result

Chip display

Add Unique ID Chip, bind unique_id field

Monospace chip (for example RST1)

Prefix + number

Uses Notion’s unique ID format

Matches what Notion shows on the page

Placement

Details (or view layout)

Often near the title / header area

Details with Unique ID Chip (Ticket ID)

Before you start

  • A Notion database with a Unique ID property enabled

  • At least one page that already has an ID assigned

  • A Details screen and Reload Data if the property is new


Step 1 — Add Unique ID Chip

  1. Open the Details screen.

  2. Add componentUnique ID Chip.

  3. Bind it to the Unique ID property (for example Ticket ID).

  4. Set a label if you want “Ticket ID” above the chip.


Step 2 — Preview and publish

  1. Select a record and confirm the chip shows the expected ID (prefix + number).

  2. Compare with the same page in Notion.

  3. Publish and verify on the live app.


Checklist


Troubleshooting

Symptom
Likely cause
Fix

Empty chip

Page created before Unique ID was enabled

Open/edit in Notion so an ID is assigned; Reload Data

Wrong format

Looking at a different property

Bind the Unique ID field, not a text “code” field

Still plain text

Old Details/Heading mapping

Replace with Unique ID Chip component


Builder options at a glance

This guide teaches a focused maker workflow. For the full screen option inventory (What it does / How to use / Why) and annotated builder screenshots, use the matching Types of Screens guide:

  • Change one option family at a time, then publish and test on phone and desktop.

  • Prefer screen-level settings in Content / Behaviour / Appearance before custom CSS/JS.

  • Keep public access and navigation visibility intentional on every screen you link from this guide.