Kinabase Logo
Help & Support

Adding Unique Identifiers

Assign distinct codes to your records


A unique identifier gives every Record

in a Collection a distinct code, such as PR-001 or INV-152, so you can locate, reference and track entries with certainty even when their names look similar.

The Identifiers configuration pane, set to the Abbreviation type

1. Why use unique identifiers

Why use unique identifiers?

  • Avoid confusion when multiple records have similar or identical names.
  • Find records fast - enter or scan a short code (e.g. INV-101) to jump straight to a specific record.
  • Communicate consistently - use the same codes across your organisation, on paper and on screen.
  • Keep an accurate history - a record keeps the same ID even if it's deleted and later restored.
  • Align with existing systems - match your Kinabase IDs to a legacy or external numbering scheme.

2. Choosing an identifier type

1. Open collection configuration

Open the options menu (⋯) in the top-right of the collection screen and select Configure, or right-click the collection name in the sidebar and select Configure.

2. Go to Details

Under Setup, click Details, then find the Identifiers section.

3. Choose a Type

Select None, Number, Abbreviation, or Custom. Each type has its own options, described below.

4. Save

Click Update to confirm. New records from this point on include an ID in the format you chose. If the change rewrites or removes existing IDs, or something already reads the ID, Kinabase asks you to confirm first - see Before you change the format below.

You'll need Configure Permission

for this collection to change identifier settings. If you're unsure, ask your System admin.

Number

Sequential, auto-incrementing IDs.

  • Prefix - a short label for the collection, e.g. PR, IMG, INV.
  • Minimum Digits - how many digits follow the prefix, from 0 to 7 (e.g. 3 digits gives 001, 002, 003).
  • Next ID - the starting number for the next new record, useful when migrating existing IDs.

Abbreviation

An ID built from letters taken from one of the record's own fields.

  • Field - the field to abbreviate, e.g. Name.
  • Characters - how many characters to include: 2, 3 or 4.
  • Include numbers in abbreviations - let digits in the field become part of the code, so Unit 7 with 2 characters gives U7 rather than UN.
  • A live Example shows the format as you configure it, e.g. "CK" is the abbreviation for "Cambridge Kinetics Ltd".

Punctuation is left out and accents become plain capitals. If a code is already in use, Kinabase adds a number, for example NFD, then NFD2. The same letter rules are available in a computed text field with ABBREVIATE - see Computed fields.

Custom

A free-form builder that combines fixed text, an auto-incrementing number, and parts of other fields - for example PROJ-{abbreviation of client name}-0001. A live Example preview updates as you build the format.

Separator sets the character between the parts: Dash (-), Underscore (_) or None. A dash or underscore is kept when the ID names an exported PDF.

Before you change the format

Other parts of Kinabase can read the record ID - a formula, a document template, a view that sorts or groups by it, a lookup field, an integration mapping or a connector data source. In Identifiers, click Usages to see those places, grouped by where they live. Click a place to open it in a new tab.

When you click Update, the confirmation lists any uses that will be affected and says what happens to existing IDs. Click Change format to save, or Cancel to keep the current format.

You can't turn identifiers off while the ID is the collection's Primary Field, or while a connector data source or an integration mapping relies on it - remove that use first. Turning off an ID that is the Secondary Field clears the secondary field. Records that link to this collection show the new ID straight away.

When existing IDs change

Turning an abbreviation or custom ID on or off, or saving a custom format with Increment for all records turned on, rewrites existing IDs. Kinabase warns that this can't be undone and that previous record IDs can't be recovered.

Changing Prefix or Minimum Digits on a Number ID also updates existing IDs, but doesn't show that warning - a number is formatted when it's read, so putting the old format back restores them.


3. Primary and secondary fields

The Primary Field and Secondary Field are separate from the ID, but often shown alongside it. The Primary Field is the field Kinabase uses to identify a record - it's shown as the record's title everywhere in the app. The Secondary Field displays alongside the primary field for extra context, for example a company name next to a contact's name.

1. Open the Fields pane

In collection configuration, under Setup, click Fields.

2. Set the Primary Field

At the top of the pane, select a field from the Primary Field dropdown, then click Update.

3. Set the Secondary Field (optional)

Select a field from the Secondary Field dropdown, then click Update. Leave it unset if you don't need the extra context.

Changing either field also updates the name shown wherever other records link to this collection. See Linked collection fields.

An identifier gives a record a unique code; the primary field gives it a human-readable name. Most collections use both - for example, an Invoices collection might show "Acme Ltd" as the primary field and INV-0142 as its identifier.


4. Identifiers on child collections

A Child Collection

has the same Identifiers settings as a top-level collection, so you can give each item its own ID. A Collection List doesn't have identifiers.

1. Open the child collection's configuration

Open the parent collection's configuration and select Lists. Under Child collections, click Edit.

2. Set the identifier

Under Setup, click Details, then set Identifiers as described in Choosing an identifier type and click Update.

In portals, IDs appear in tables but are hidden from add and edit forms, since IDs are generated by Kinabase.


5. Migrating existing IDs

If you're moving from another system and want to keep your existing numbering scheme:

1. Set the prefix

Match your old format, e.g. IMG.

2. Adjust Next ID

Set it to one higher than your last used number, e.g. 153 if your last record was 152.

3. Save your changes

New records continue the numbering without creating duplicates.

Why identifiers might skip numbers

  • Deleted records - every record gets an ID, even one that's later deleted. Once a number is used, it's never reused, avoiding any confusion or duplication.
  • Preserved history - this keeps a consistent audit trail, so if a deleted record is restored, it keeps its original ID. See Deleting and restoring records.

Once a record is created, its ID doesn't change, even if its fields are edited later. Changing the ID format can rewrite existing IDs, as described above. Plan your format carefully if you have existing data or a legacy numbering system to align with.


6. Show the ID in a computed field

A Computed Field

can show the ID Kinabase assigns, or build a label from it - for example a reference such as JOB-0042-LDN. The ID is filled in as soon as a record is created, including records added by CSV Import , so the computed field shows the ID the record will keep.

1. Reference the ID

Open the computed field from Fields under Setup. In Template, type $ and select ID. A Number computed field can also use Numeric ID, the record number without any prefix.

2. Use a computed field in a custom ID

Under Identifiers, set Type to Custom, click Add part and select Field (e.g. Company Name) to include a computed field's value. Click Update to save.

Avoiding a circular loop

A custom ID can't use a computed field that itself depends on the record ID, directly or through other computed fields - the ID would depend on itself. Kinabase names the field that causes the loop in the Formula or Template editor, and won't save the formula or the Identifiers until you change it.

Using Numeric ID is fine, because the number is assigned before the custom ID is built.

When you change the ID format in a way that rewrites existing IDs, computed fields that show the ID are recalculated too, along with any aggregation fields that depend on them.

For more on writing the formula, see Use the record ID.


Configuring unique identifiers keeps large collections organised and makes every record easy to find, reference and track, even as your data grows.


Need more help? Ask your System admin, or contact our support team via Help & Support.