Fieldset
The Fieldset field shows a group of fields which are configured as Fieldset schema e.g., for an address, you need three fields "street" (text), "zip" (number), "city" (text) which you can group as one field (*fieldset) "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
Picturepark Setup 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:
JSON
A multi-tagbox value in a single fieldset: ![]()
JSON
|
Advanced search for field | |
Use in the display pattern | |
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 otherwise happen that the business rule connects the value from the first entry (array) with the key from the 2nd entry (array). |
Returned field value | Single:
|
Fieldset Field Settings
Name | The setting "name" is available for various things in Picturepark e.g. fields, schemas, business rules. This value defines what appears in the Picturepark interface. You can change the name at any time, and translate it into any configured metadata language. If you would like to add a translation for the name, just press Add.
|
ID | The field id is the ID of your field, which is used to link to this field. The field id is always lowercase. The id of the field is set on the creation of a new field, using camel casing. You need the field id for the configuration of filters or display pattern. 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. |
Sortable | Sorting based on fieldset values not supported. |
Include in filters | Filtering based on fieldset values 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 setting "View for all" applied per 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 that cannot view a Content Item in a relationship field he will get this view:

However, double-clicking on that field will allow him to view the relationship details:
