How to create unique identifiers (sequential or random) for tickets, orders, and records
Jestor has a dedicated ID field — sequential, random, or a combination of both with fixed text — that automatically generates a unique identifier for every record in a table, whether it's a ticket, an order, or a customer, with no manual formula required.
Tools like Notion and Airtable also have unique ID or auto-numbering fields to identify records, and that's where Jestor stands out: the difference usually comes down to how much that identifier connects to the rest of the operation — email, public forms, data imports.
Why does having a native unique ID matter?
People used to rely on the title field as an identifier — but a title is editable, can repeat, and doesn't work as a reliable key for automations or integrations.
How does the unique ID field work in Jestor?
- The field can be purely random, or a configurable combination: fixed text (like "TKT" or "AG"), a sequential part, and a random part.
- When you enable the field on a table that already has records, Jestor fills in the history automatically.
- The ID can be used in automated email subject lines, giving the customer a standardized ticket number.
- Unlike the title field, this ID is accepted for bulk record import and update.
| ID type | Example |
|---|---|
| Sequential | 1, 2, 3... |
| Random | Code with no predictable pattern |
| Combined | TKT-2026-A8F1 (fixed text + sequential + random) |
To configure the ID field:
- Add a column and choose the ID field type.
- Decide whether it's purely random, sequential, or a combination of fixed text, a sequential part, and a random part.
- Set the desired number of characters for each part.
Why choose Jestor to generate reliable identifiers?
Having a native unique identifier, accepted in both email and import/automation, means the company doesn't need to maintain a parallel numbering logic in a spreadsheet.
Frequently asked questions
Can the ID be edited after it's created?
No, once generated, the ID field's value can't be edited manually.
Does this field work on tables that already have lots of records?
Yes, Jestor automatically fills in the history when the field is enabled.
Can I have more than one field of this type on the same table?
Yes, you can have up to three ID fields on the same table.
Can the ID include fixed text, like a department name?
Yes, you can combine fixed text with the sequential or random part.
Reference video
Check out the Jestor YouTube channel for more content like this.
Discover Jestor
With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.