How to use unique IDs to protect public forms and avoid data import errors

Using a random ID field instead of the title field as an identifier makes it harder for someone to guess or accidentally access another record's link in a Jestor public form, and it also solves a recurring problem for anyone who tried to use the title as a key to bulk-import records.

Why does using a unique ID on public forms matter?

Public forms that use a predictable identifier in the link make it easier for someone to try to guess the link to a record that isn't theirs. And anyone working with spreadsheet imports runs into a similar problem: the title field isn't accepted as a key by Jestor's importer.

How does a unique ID protect forms and improve imports?

Instead of the title, the random ID field generates a code with no predictable pattern.
This doesn't replace other security layers, but it closes a gap that existed when using a visible, sequential identifier.
For bulk record import and update, the ID field, unlike the title, is accepted as a key by the importer.
The same field also works to identify records within automations.

Field used as key	Accepted for bulk import?
Title	No
Unique ID	Yes

To use the ID as a secure key:

Add a random ID field to the table.
Use that field — not the title — as the reference in public form links.
Use the same field as the key column in import or update spreadsheets.

Why choose Jestor to protect data and imports?

Having a field specifically designed to serve as a secure, reliable key means the company doesn't need to repurpose the title field, which was built for display, for a use it wasn't meant for.

Frequently asked questions

Does a random ID completely prevent unauthorized access to a public form?

Not by itself — it makes guessing harder, but doesn't replace other security practices.

Why doesn't the title field work for imports?

Because Jestor's importer doesn't accept title as a key; you need to use the ID field.

Can this ID be used in automations?

Yes, it reliably identifies a specific record.

Do I need to change the identifier on tables that already exist?

It's not required, but it's recommended for anyone using public forms or bulk imports.

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.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize