12d - Asset metadata field types and how they map

Info: This article is work in progress and subject to change.

When you configure a Field in the Workflow Assistant Configurator, the Field name option binds the Field to a real Assets metadata field. Not every Configurator field type can bind to every Assets metadata type — the autocomplete in the Field-name option only offers Assets fields that match the Configurator type you have chosen.

This appendix is the working reference for the mapping. Use it when planning a new field, when migrating between Assets versions, or when troubleshooting a field that does not behave as expected.

For the Configurator field types in detail, see 05a — Fields reference.

The mapping

How the autocomplete enforces the mapping

When you set the Field name option, the autocomplete shows only Assets fields whose type matches the Configurator field you have chosen. A few consequences:

• If you change a Configurator field’s type after binding, the autocomplete will likely no longer show your previous Field name. Re-pick from the autocomplete to bind a compatible field
• If you paste a Field name that is not in the autocomplete list, the Workflow Assistant errors at runtime when an end user opens the panel. Always pick from the autocomplete
• If the field you expect is not in the autocomplete, the Assets schema does not have it (or has it under a different type). Coordinate with your Assets administrator

Note: The “non-existent field name causes runtime error” behaviour is the most common silent mistake reported to support. The Configurator does not warn at edit time — only when the panel is opened by a real user. The autocomplete is your protection; never bypass it by pasting.

Case sensitivity

Assets metadata field names are case-sensitive. assetDomain, assetdomain, and AssetDomain are three different fields, only one of which exists in your Assets schema.

Always pick from the autocomplete; never re-type the field name from memory. The autocomplete preserves case correctly.

Multi-value fields

A multi-value Assets field holds a list of values rather than a single value. The Workflow Assistant exposes them through the Tags type, which adds and removes values one at a time.

Note: A Configurator Dropdown field is single-value, even though it presents a list of choices to the user. It binds to a single-value Assets text field. To present a multi-pick interface, use Tags.

Custom fields

Assets supports custom fields defined in the Custom asset info file. The Configurator treats custom fields identically to system fields — they appear in the autocomplete based on their type, just like any other field.

Common custom-field naming conventions you will see:

The prefixes are conventions, not enforced. Confirm the field’s type via the autocomplete before binding.

When migrating between Assets versions

If you are migrating a panel configuration between Assets 6 and Assets 10 — or between two Assets installations of the same version — a few field-mapping checks save time:

Step 1. List every Field name used in the panel.

Step 2. For each, confirm the destination Assets installation has a field with the same name and the same type. Use the autocomplete in the destination’s Configurator to verify.

Step 3. For any field that does not exist in the destination, decide whether to add it to the destination Assets schema (preferred), replace it with a different field in the panel, or remove the Field from the panel.

Step 4. After migrating, sign in as a test user in the destination environment and verify every Field renders and accepts input. A silent error appears as a missing or unresponsive field — not as a visible error.

See 10 — Working across Assets 6 and Assets 10 for the broader migration playbook.

Cross-references

• 05a — Fields reference — every Configurator field type
• 10 — Working across Assets 6 and Assets 10 — the migration playbook
• 02b — Component types — Field is one of three component types

Revisions

• 8 May 2026: First publication of the manual