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.
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

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
Open the Details screen.
Add component → Unique ID Chip.
Bind it to the Unique ID property (for example Ticket ID).
Set a label if you want “Ticket ID” above the chip.
Select a record and confirm the chip shows the expected ID (prefix + number).
Compare with the same page in Notion.
Publish and verify on the live app.
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
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:
Data screens: List (View Items), Details, Form (Add Item), Form (Update One Item), List (Update Items), Content
Everyday chrome / Queue & activity: see the Types of Screens index
Automation native screens: Native Automation Screens
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.