Open or create the schema where you want to add a field, such as a list, layer, virtual type, fieldset, or relation.
Open schema settings by double-clicking on the schema.
Select the Fields tab in the right column of the schema detail view.
Add one or multiple fields, remove fields - make the necessary changes.
Save your changes.
The status in the left column has a red mark to indicate that you must re-index the search indexes after you make changes to fields.
Get the field path
Access the Field Path
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.
CODE
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
You can open the Display Pattern Editor to see the JSON of a Content Item.
Get the field id
Access the Field ID
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
You can open the Display Pattern Editor to see the JSON of a Content Item.
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.
Reuse a Field Name or Field ID
Reuse a Field Name or Field ID
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.
Now, you can use the same ID and change the field type.
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.
Update the order of a field
Update the Field Order
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.
Double-click on the schemas.
Edit the fields in the right column of the schema details.
Drag and drop the fields into the correct order
Save
Video on how to re-order fields in the edit mode (when editing fields).
You cannot reorder fields on a child that is propagated from a parent. Those fields are always at the top. The Save button will be greyed out.
Delete a field
Delete a Field
Open the schema where you want to edit a field, such as a list, layer, virtual type, fieldset, or relation.
Open settings with the gear icon.
Find your field.
Edit fields (click edit or use shortcuts)
Select the x to remove the fields you want.
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.
The field will not be removed from Filters or Display Pattern they are referenced in. You need to do this manually.
What could happen is:
Display of "Invalid template" in display patterns if you worked with liquid tags