Field rules
Required, unique, immutable, options, pattern, min and max, currency unit and defaults — and the messages you see when a value breaks a rule.
Rules keep your data clean. They are checked every time a record is created, edited, imported or changed by a flow, a form or Ask Axis. This page lists every rule a field can have and the message you see when a value breaks it.
Flags
| Flag | What it does |
|---|---|
| Required | A record cannot be created without a value, and an edit cannot leave it empty. The form shows * after the label. |
| Unique | No two records of the type can share a value. Email addresses are compared ignoring capitals. |
| Immutable | The value can be set once and never changed. The first value is allowed when the record is created, or later if the field was empty. |
A field can be required, unique and immutable at the same time. A computed or auto-numbered field cannot be required, unique or immutable.
Rules by type
| Rule | Applies to | Details |
|---|---|---|
| Options | select, multiselect |
Value must be one of the options. At least one option is needed. |
| Pattern (optional) | string |
A regular expression (RE2). The whole value must match it, for example ^SKU-[0-9]+$. |
| Min / Max | number, currency |
Value must be at or above the minimum and at or below the maximum. Min cannot be greater than Max. |
| Currency unit | currency |
A 3-letter code. When set, every value uses that currency. |
| Points at | ref, refs |
The record type the link goes to. |
| Default | most types | Filled in when a new record leaves the field empty. Must itself be a valid value. |
Length limits that always apply: string and file up to 500 characters, text up to 100,000, lists (multiselect, refs) up to 100 entries.
Validation messages
The record form shows the message under the form after you click Save or Create. Messages start with the field's key.
| Message | Cause |
|---|---|
<key>: required field missing |
A required field was left empty on a new record. |
<key>: required field cannot be cleared |
An edit tried to empty a required field. |
<key>: required field is empty on this record — fill it in to save |
An older record has an empty required field and you saved without filling it. |
<key>: immutable: value cannot be changed after creation |
A write-once field already has a value. |
a unique field already holds this value |
Another record already uses this value in a unique field. |
<key>: does not match pattern |
A string value does not match the field's pattern. |
<key>: must be one of the configured options |
The value is not one of the options. |
<key>: must be >= 10 / must be <= 100 |
Outside Min / Max. |
<key>: expected a decimal with up to 14 integer and 6 fraction digits |
A number has too many digits or is not a number. |
<key>: not a valid email address |
Bad email value. |
<key>: must be an absolute http(s) URL |
url values must start with http:// or https://. |
<key>: expected YYYY-MM-DD |
Bad date value. |
<key>: must be at most 500 characters |
Value too long. |
Rules are not retroactive
A new rule applies from the moment you add it. Records created earlier are not rewritten. For example, if you make a field required, older records with an empty value stay as they are and cannot be saved until the field is filled. The Data quality check finds them for you.
Note: A link (
ref) is checked for its shape only. AxisIQ does not stop you deleting a record that others point at. The data quality check reports links that point at records that no longer exist.