Open or create the schema where you want to add a field, such as a list, layer, virtual type, fieldset, or relation.

1. Open schema settings by double-clicking on the schema.
2. Select the Fields tab in the right column of the schema detail view.
3. Add one or multiple fields, remove fields - make the necessary changes.
4. Save your changes.

The field path is the hierarchy of the field, which is the path where you can find the field. To configure filters or display patterns, you must access the value via field ID or field path. The field path always starts in lowercase. 

layerId.fieldId

You can open Schemas > Indexing. There, you find the field path of every field of the schema. To copy it. click on the value.

• Visual representation of the hierarchy of the field path syntax
  • productInformation.products
  • descriptiveKeyword.keywords
  • multimediaInformation.sources

The ID fieldis 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 for the configuration of filters or display patterns. 

The ID is automatically created from the name you insert: 

• Example: You insert the field name "My NeW fielDs #1 Purpose?
• Automatic Id: myNeWFielDs1Purpose

Search: Find Items by Product Codes (Solutions)

Search: Check if Field Product Description Exists (Solutions)

Search: Find Product Information in Translated Description (Solutions)

Search: Find Items with Tagbox Values (Solutions)

Search: Find Items with Checkbox Values (Solutions)

Search: Find Items with Fieldset values (Solutions)

Search: Find Items with specific values in text fields (Solutions)

Search: Find Items with values in translated fields. (Solutions)

Search: Find Items with Exact Term in Translated Field (Solutions)

Search: Find Items with Value in a Field (Solutions)

Search: Find Items where Field or Layer is Empty (Solutions)

Open the schema where you want to edit a field, such as a list, layer, virtual type, fieldset, or relation.

1. Open the settings with the gear icon.
2. Select fields in the sub-menu.
3. Find your field.
4. Select the edit icon next to it.

Video on how to update an existing field.

Some settings cannot be changed:

• Field Type
• The ID of the field
• Specific field properties:
  • Allow only single or multiple items for fieldset, relationships, and tagbox
  • Add translations for text fields
  • From date to date time and vice versa
  • From number to decimal and vice versa

When updating search settings, check the main menu for search indices badges and open the settings to reindex if required.

When updating the required flag, some items may be missing the new required values. Content Platform will display a message to inform you about this. However, there is no actual check to see if content items are affected. Admins must search for the field to find affected content items and batch edit them to add the required values. (see the search for a field). The required check does not work for fieldsets and relations. You must open the fieldset schema and check its usage in the overview panel – this does not work again for nested fieldsets (fieldset in fieldset in fieldset). Consider a batch edit or Excel update to ensure data integrity.

Open the schema where you want to re-create a field with a different ID or field type, e.g., a list, layer, virtual type, fieldset, and relation.

1. Open the settings with the gear icon.
2. Select fields in the sub-menu.
3. Find your field.
4. Remove the field.
5. Check the main menu for search indices badges and open the settings to reindex.
6. Re-open the schema and add your field again.
   1. Now, you can use the same ID and change the field type.
   2. You can create the field as a new field.

When the field is removed, all values are removed. Please export all values via Excel Export and use this Excel to populate the new field with the correct values.

This order is used for input, so it's the order users see. Open the schema where you want to update the order of fields, for example, a list, layer, virtual type, fieldset, and relation.

1. Double-click on the schemas.
2. Edit the fields in the right column of the schema details.
3. Drag and drop the fields into the correct order
4. Save

Video on how to re-order fields in the edit mode (when editing fields).

Open the schema where you want to edit a field, such as a list, layer, virtual type, fieldset, or relation.

1. Open settings with the gear icon.
2. Find your field.
3. Edit fields (click edit or use shortcuts)
4. Select the x to remove the fields you want.
5. Save.

Remove, Add, Update in Edit Mode..

If you delete a field, you can only reuse the same ID when you update the status of Content and List Items from the Settings. Check the Main Menu for a badge that informs you about the necessity of performing an update. Removing a field from a parent and adding the field to another parent works just fine without status updates.

What could happen is: 

• Display of "Invalid template" in display patterns if you worked with liquid tags
• Empty Filter in the Content Browser

• Common Field Settings

Each field has a set of attributes that affect how the field behaves. You configure the settings when adding the field to a Layer or Virtual Type, so different instances of the same Field Type can behave differently, depending on their specific settings. Some parameters are common to all the field types. 

• Checkbox

The Checkbox field is on or off (technically, that means true or false, so-called Boolean). Its meaning depends on the label e.g. Checkbox "PermissionDenied" ✔ means permission denied, whereas checkbox "PermissionApproved" ✔ means permission granted, although the checkbox in both cases has the same value (true), the understanding is different based on the label.

• Text

In the Text field, you can insert text, numbers, and special characters, which means unstructured information, as the user can write whatever they want - even High Valyrian, Valar morghulis, which almost nobody understands. Text fields, therefore, should have a clear label indicating their purpose, for example, Public social media description (avoid company bashing) or similar.

• Fieldset

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 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).

• Relationship

The Relationship field allows relating content to other content, similar to hyperlinks (links) on the internet, and is especially useful for creating press kits, print packages, and landing pages by adding related visual content. For a press kit, you can link the hero image and the Logo. 

• Date Time

The Date Time field allows input of a date or a date and a time, which display and interpretation you can specify as format, e.g., show dates with year/month/day or day-month-year.

• Geo Point

The Geo Point Field has two number fields for adding longitude and latitude values. Applications like Google Maps use this kind of Geo-Information about a location. In Picturepark you can only use Geo Point values in Query Filters. 

• Number

The Number field contains only numbers. If you are unsure if the expected values may contain text, then use a text field. Otherwise, use the Number field. The benefit is that you can calculate with numbers but not with text. For example, 2+2=4, but "Content" + "tent" is nothing.

• Tagbox

The Tagbox field allows you to tag content, similar to tagging in social media, but with the option to configure the available tags. Tags work as a grouping of content. Tags are structured information because users cannot make typos when selecting from a predefined list. You can use Tags for regions, locations, moods, colors, product categories, countries, and almost everything. You can click directly in a tagbox field to display a drop-down list of suggestions, or, you can select this iconto open a dialog where you can bulk select several list items. You can also search, filter, sort, and create new list items in this dialog.

• Trigger

The Trigger field you can use to trigger a business rule with the benefit that it stores the information about the user who clicked the field and when (date and time), whereas a checkbox "start business rule" would not have any information about user and time.

• XMP Mapping

XMP Mapping allows the extraction and import of XMP/EXIF data into Picturepark metadata fields and the exporting of data from Picturepark metadata fields into XMP based on field mappings. The XMP handling happens when importing files into Picturepark or exporting from Picturepark. XMP Mapping must be enabled for the required output formats via API so that the downloaded output format contains the data.

• Display Pattern

Display Patterns are configurable templates in Liquid Syntax (used in Shopify). In these Patterns, you take metadata and other values and construct a nice piece of information.

{% if data.fruit.shortDescription%}
{{data.fruit.shortDescription | translate | truncate: 250}}
{% endif %}

<br><be>

Product: {{data.fruit.code}} - {{data.fruit.name}}
<br>
Bricks class: {{data.fruit.bricks | tagbox_list | join: ", "}}
<br>
{% if data.fruit.price%}
Price: {{data.fruit.price}} {{data.fruit.currency.code}}
{% if data.fruit.unit%} per {{data.fruit.unit.name | translate}}{% endif %}
{% endif %}

{% if data.fruit.supplier %}<br>Supplier: {{data.fruit.supplier | tagbox_list}}{% endif %}

The configuration supports different metadata values and static text combinations, including translations and tags. For configuration, you should be familiar with the field types in Picturepark.

Display patterns are configured for Virtual Types, Layers, File Types, Lists, and Fieldsets. Some Display Patterns may not yet be in use. Picturepark generates a display pattern for you when a text field is assigned. It will take the first available text field and display its value, if there are any.

• Dynamic View

The Dynamic View field allows relating content to other content based on metadata or other criteria, for example, relating content with the same document number or relating content with the same product number or the same event. This is especially useful for creating language versions of documents, product packages, or other content collections.

• Tree View