Table of Contents
Fieldset
18. May 2026
Table of Contents
The Fieldset field shows a group of fields configured as a Fieldset schema. For example, for an address, you need three fields: Street (text), Zip (number), and City (text), which you can group into a single field (*fieldset) named Address. This grouping allows you to have a set of fields for adding address information, always available as one field (*fieldset).
Fieldset overview
| Icon |  |
| Pre-Requirement | Before creating a fieldset, first, create the underlying fieldset schema (a group of fields). |
| Limitation |
Not available in batch edit mode of the Batch Editor! Only Single Fieldset fields are available in the Excel Roundtrip App. |
| Parent-Child Setup |
You can create a schema "Fieldset" following a parent-child setup. When you connect your Fieldset schema to the Fieldset field, the parent-child hierarchy is ignored. If you connect the Fieldset field to a parent, you will only see fields on the parent. If you connect the Fieldset field to a child, you will only see fields on the child, no propagated fields from the parent. |
| Single Fieldset | One data entry using the underlying source schema, e.g., one copyright information for an image (there shouldn't be more than one). |
| Multi Fieldset | Multiple data entries, each using the underlying source schema. |
| Behavior |
Video on how the fieldset for a single item behaves |
| Examples |
|
Fieldset value handling
| Fotoware Alto S,etup Example |
Layer: Corporate Information (ID: CorporateInformation) Field: Duration (FieldId: duration) Fieldset Schema Fields: Start (ID: start), End (ID: end) |
| Fieldpath | corporateInformation.duration.start |
| Excel Roundtrip App | LAYER.FIELDSET-FIELD.SOURCE-FIELD |
| Default Value in Business Rule |
A fieldset value:
A multi-tagbox value in a single fieldset: 
|
| Advanced search for field | Search: Find Items with Fieldset values (Solutions) |
| Use in the display pattern | Display Pattern: Fieldset (Solutions) |
| General Access |
To get the display pattern from the fieldset: To get the fieldset schema name: To get a specific value in single fieldsets: |
| Use in the business rule | The Business Rules do not check the value pairs in the correct order, and therefore, fieldsets shouldn't be used. It may happen that the business rule links the value from the first entry (array) to the key from the 2nd entry (array). |
| Returned field value |
Single:
Multi: Array
|
Fieldset field settings
| Name |
The Name setting is available for various items in Fotoware Alto, for example, fields, schemas, and business rules. This value defines what appears in the P interface. You can change the name at any time and translate it into any configured metadata language. To add a translation for the name, select Add.
|
| ID |
The ID field is the ID of your field, which is used to link to this field. The field ID is always lowercase. The field's ID is set when creating a new field using camel casing. You need the field ID to configure ID filters or display patterns. The ID is automatically created from the name you insert:
 You can open the Display Pattern Editor to see the JSON of a Content Item. |
| Single item fieldset |
Allowing one or multiple data entries into the fieldset field. This setting cannot be changed afterward. A case for a single fieldset:
A case for a multi fieldset:
|
| Source | The underlying fieldset schema. |
| Required | The Required field setting determines whether or not an editor must provide a field value before being able to save the Content Item. If a field is required and the user has not provided a value or deleted an existing value, Fotoare Alto prevents UI-required, and if the user has not provided a value or deleted the existing value, Content Platform prevents saving the item. This value can be changed at any time. You cannot set a field to required on a Layer when any field has XMP mappings defined. The Required field setting is unavailable for checkboxes, trigger fields, or dynamic view fields. |
| UI required | The UI required field setting determines whether or not an editor must provide a field value to save the Content Item in the UI. If a field is UI-required and the user has not provided a value or deleted the existing value, Content Platform prevents saving the item in the UI. This value can be changed at any time. The UI required field setting is unavailable for checkboxes, trigger fields, or dynamic view fields. |
| Sortable | Sorting based on fieldset values is not supported. |
| Include in filters | Filtering based on fieldset values is not supported. |
| Include in search | All entries in a Fieldset are indexed. When the search finds a match, the parent Content Item is displayed. |
| Boost value | The search does not consider the boost settings of the underlying fieldset schema. |
Fieldset schema permissions
- Relationships and Fieldsets have the "View for all" setting applied by default. This cannot be changed, and the button is grayed out.
- It is therefore important to ensure that you protect fieldsets and relationships behind layers and disable the View to All on these Layers.
For example, if you have a user who cannot view a Content Item in a relationship field, they will get this view:
However, double-clicking on that field will allow them to view the relationship details:
