Skip to main content
Skip table of contents


The Text field allows us to insert text and numbers and special characters which means unstructured information, as the user can write basically what he wants - even high valyrian "Valar morghulis" which eventually nobody understands. Therefore, text fields should have a clear label e.g. "Public social media description (avoid company bashing)" or alike.

Text Overview



Video on how a text field without translations behaves

Text Area

Video on how a textarea with translations behaves

Text with Translations

Video on how a text field without translations behaves

Text with Markdown

Text fields in Picturepark have an additional option to render Markdown. Using Markdown in text fields allows for basic formattings like the use of headlines, bold, italic for descriptions, press kit content, or product details, to highlight specific areas or structure longer texts. Picturepark shows an editor with a side-by-side view for formatted and unformatted text.

Picturepark uses the following component for rendering: which offers an online demo. Please ensure that all plugins (checkboxes at the top) are disabled in this demo, as Picturepark does not support any plugins for now. Some basic examples of Markdown syntax are:


Text fields allow limited control for user input. Whenever you work with text fields you may have typos or dummy text. The only control present for text fields is the definition of a regular expression for text input. 

Text input is always unstructured content. 

Filter and Analyzer

You can add a filter for text to the Content Browser. Be aware that you might end up with a lot of filter values as text entries can differ a lot, also they may speak about the same topic. Consider to Tagbox fields to avoid three different filters for the same topic:  

  • Title: New Office Location in Aarau

  • Title: Aarau New Offices

  • Title: The new location of the Aarau Office

Text input is analyzed in Picturepark. Analyzers are explained in the Search Analyzer Section. Analyzed means Picturepark extracts individual relevant terms, whereas relevant depends on the Analyzer. 

  • Text without translations is analyzed with a simple analyzer. 

  • Text with translations is analyzed with the language analyzer. 

  • Further analyzers can be configured. 

Usage as sort fields

You can use translated text as a sort field for a Channel. You can configure a) the field itself or b) the specific language of the field.

a) For the field itself, changing the UI language will trigger the sorting to work against the corresponding translation value.

b) For the specific language, the sorting will also happen only on the configured language. This enables you to sort on metadata languages other than English and German if the values are translated. 


Use the Text field for:

  • Product Codes

  • Titles

  • Descriptions

  • URL

Text Value Handling

Picturepark Setup Example

Layer: Corporate Information (ID: CorporateInformation)

Field1: Title (ID: title, translated text)
Field2: Note (ID: note, text without translations)


Path: corporateInformation.title.en
Path: corporateInformation.note

Advanced search for field


Use in Display Pattern

Returned field value

The Liquid filter | translate returns the value that matches the default language. 

To get specific language values you must provide the correct language abbreviation: .de / .en

Text Field Settings


Add the name in singular or plural depending on the use case. 

Avoid adding the required language in the label (Title English, Titel Deutsch) as Picturepark shows the language in front of the field. 


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: 

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


It defines that the field value must be displayed in a multiline component.
This setting has no effect on the possible input but on the user experience as the multiline display is easier to read for longer text.


The option to render the text values as Markdown, including side-by-side Markdown editor. Picturepark offers:

  • Default rendering: The text input is just text without any formatting.

  • Markdown rendering: The text input is in Markdown syntax and bold, italic and links are rendered correctly.

Markdown will only be rendered in the Content Item Detail View, not in Display Pattern or list views.


If a field is a translated string or not can not be changed anymore once created. Make sure you use translated strings where needed (or might be needed). Keep in mind that translated fields are "expensive" for indexing


The field setting "required" determines whether 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 has deleted an existing value, Picturepark does not permit saving the item. This value can be changed at any time. You cannot set a field required on a Layer that has XMP mappings defined for any field. 


The field setting "sortable" for a field defines if Picturepark uses the values of those fields for sorting of List Items (in Lists). Sorting of contents based on fields in a Layer is possible via the channel configuration, which only considers fields marked as sortable. All fields except for Geo Point and Relationship fields are sortable. This can be changed after field creation. 

Minimum characters

The minimum amount of characters a user must provide. This may be useful to avoid entries like "tbc" or "temp". 

Maximum characters

The maximum amount of characters a user can provide. This is useful to avoid breaking layouts due to very long text. This is also useful for text entries that will be used for Social Media which only allow a certain amount of characters e.g. Twitter only allows 280.

Regular expression

Only for input validation means you can force the user to insert a valid email address, but you cannot append something after input - this can be achieved with a calculated value.

A JSON Schema regex can be used. See here for valid examples:

North American telephone number with optional area code - 555-1212 is valid but (800) Flowers is invalid:


Calculated value

You will not be able to enter text in this field if switched on. The value pattern will be displayed in view mode.

Due to the performance for creating content or list items that have relationship fields, a limitation on the calculated values is present. A calculated value won't be able to access the data of the linked (and resolved) list items. It will only be able to access base content information and the other metadata information (other fields, fieldsets, and relationship values). If the values of linked list items are used, their value is simply not resolved, but the rest of the specified template is rendered. No error message appears if a calculated value cannot be resolved that part of the calculated value just doesn't display.

Once the calculated value setting is switched on you cannot just switch it off to remove the calculated values.

  • You can update the calculated values.

  • You can remove the calculated values by batch editing all affected items (List, Content) and remove the value or you can remove the field.

Value pattern

Monaco Editor which allows defining the calculated value pattern in Liquid Syntax.

  • Display Pattern: SEO Friendly Title

    A slug is an SEO friendly title you use for images, videos, or complete press kits when sharing them on social media. Picturepark can create the slug for you using any value from any field, replacing spaces with dashes, and even pretending the correct domain. {{data.corporateLayer.title.en | replace: " ", "-" | prepend: "" }} {{data.corporateLayer.title.en | replace: " ", "-" | prepend: data.corporateLayer.domain }}

  • Display Pattern: File Metadata in Layer Fields

    You may want to show the file extension or original filename (standard file metadata) in calculated text fields in a layer. You can make those available to the search and have some basic information shown. {{ | replace: ".", " " | upcase}} {{}} {{}}

Include in filters

The field setting “Include in filters” allows the field to be added as a filter for content (see Channels Configuration) and the field values to be edited in the Batch Editor (indexed fields). Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit, and by testing your common search scenarios - too much values will not automatically result in better search results.

Include in search

The field setting "Include in Search" determines whether the field's values should be considered in content browser simple search operations. If this option is not enabled, the search does not consider the values of the field in search operations. This can be useful, for example, if the field is used for internal discussions or work directives that you don't want to affect the search results. Picturepark checks those settings against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit.

Boost value

The field setting "Boost" will boost the values in the search and helps you define the relevance of the content for your users. The boost parameter increases the relative weight of a term (with higher boost values) or decreases the relative weight (with lower boost values), but the increase or decrease is not linear. In other words, a boost of 2 does not result in double the score. You can select between 1, 10, 25, 50, 100, or 500. 

  • Boosting in a list is for the search in fields while tagging.

  • Boosting in layers is for the content browser search.

Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit.

Filter analyzer

Search Analyzers used for creating values from the input for Filters in the sidebar. Check Analzyers for details. 

Simple search analyzer

Search Analyzers used for creating values from the input for the Simple Search. Check Analyzers for details. 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.