Skip to main content
The Constant field always resolves to one fixed value you configure. Every record gets the same value, and submitters never type it.
Constant is a computed field. Its value is system-generated from the setting you configure, the field is always required, and it does not appear as an input a submitter can fill in.

​
When to use it

Reach for Constant when the same value belongs on every record:
  • A fixed label such as a source-system name, a channel, or a version tag.
  • A constant segment inside a Concatenation field, so you do not retype it on every submission.
  • A marker that tells records produced under one model apart from another.
Do not use Constant when the value differs between records. Use a Dropdown for a controlled set of choices, or Text for free input.

​
How it works

Every record gets the configured value, identical across all of them. Because the value is generated for you, the field is not shown as an input in the submission form.

​
Settings reference

SettingRequiredDefaultDescription
valueYesNoneThe fixed string written to every record.

​
Example

A channel field on a Campaigns taxonomy, used to fold a fixed UTM value into a tagged URL: 
name: channel
type: constant
settings:
  value: "newsletter"
Every campaign record created while this model is published gets channel = newsletter. A Tagged URL field can then read this value into its utm_medium parameter without anyone retyping it.

​
Gotchas

  • Changing value does not backfill. Existing records keep the value they had when they were approved. Editing the setting and publishing again affects only new submissions.
  • It is the same on every record. That is the point. If you need variation, this is not the right field type.
  • It is read-only. The value is generated for you and there is nothing to edit in the submission form.