Clone

Pro

A Clone field reuses fields defined in another fieldset. Build an "Address" fieldset once, then clone it into Books, Writers and user profiles. Change the original, and every clone follows.

Settings

• Source fieldset: the fieldset whose fields you reuse. You edit the fields there, not in the clone.
• Fields to include: pick some fields, or leave it empty to include all of them.
• Display: Seamless (inline with siblings) places the cloned fields directly in this fieldset as if you'd added them here. Group (nested under this field) keeps them together under the clone's own key, like a Group.
• Key prefix: added to the start of every cloned key, such as billing_. You need it when you clone the same source twice into one fieldset, for example a billing and a shipping address. Conditional logic between the cloned fields follows the prefix: a rule on State that reads Country reads billing_country in the billing clone.

How values are stored

A clone stores nothing of its own. With seamless display, each cloned field stores its value under its own key (plus the prefix), exactly like a normal field. With group display, they're stored together under the clone's key.

Because seamless clones add real keys to the fieldset, they count towards key conflicts just like other fields.

Limits

• A clone can't include another clone. Clone fields in the source are skipped.
• Inside a Field Table or Content sections, clones must use Group display.

Technical details for LLMs

• Type key: clone (Pro). Settings: source_fieldset, source_fields (empty = every eligible top-level field), display (seamless | group), prefix.
• Expanded at runtime into the source's fields before saving, reading, REST and dynamic data. The clone itself has no stored value and isn't writable over REST.
• The prefix applies to every key of the cloned scope, those inside the source's sections and tabs included, and to the head of any cloned rule that names one of them. Sections and tabs come along with their keys moved under the clone's (clone_key/section_key).
• Nested clones (clone chains) are dropped and flagged on save. seamless isn't allowed inside table or content_sections.
• Duplicating a fieldset copies clones as-is.