Fields
- Elaine Foley
Create a Field
Open or create the schema where you want to add a field, e.g., a list, layer, virtual type, fieldset, and 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 all changes.
Save when your work is done.
The status in the left column has a red mark to indicate that you have to re-index the search indexes after you made changes to fields.
Access the Field Path
Access the Field ID
Search for Specific Field Values
-
Page:Search: Find Items by Product Codes (Solutions)
-
Page:
-
Page:
-
Page:Search: Find Items with Tagbox Values (Solutions)
-
Page:Search: Find Items with Checkbox Values (Solutions)
-
Page:Search: Find Items with Fieldset values (Solutions)
-
Page:
-
Page:
-
Page:
-
Page:Search: Find Items with Value in a Field (Solutions)
-
Page:Search: Find Items where Field or Layer is Empty (Solutions)
Update a Field / Edit a Field
Open the schema where you want to edit a field, e.g., a list, layer, virtual type, fieldset, and relation.
Open the settings with the gear icon.
Select fields in the sub-menu.
Find your field.
Select the edit icon next to it.
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
Adding 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 miss the new required values. The Content Platform shows a message to inform you about this. However, there is no actual check 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.