Skip to main content

Cookie control banner

Necessary Cookies
These cookies are necessary for this website to function correctly. They are set when you perform certain actions on the site, such as creating an account, logging in, changing your privacy preferences or submitting a form. You can block these cookies in your browser, but this will stop parts of the site from working properly.
Functional Cookies
These cookies allow the website to provide extra functionality and more personalised experiences. They may be set by us or by third party providers whose services we have added to our pages. If you choose not to allow these cookies, these services may not work correctly.
Analytical Cookies
These cookies record anonymous data on how visitors use our website to help us monitor how well our website works. This data includes how many people have looked at specific pages, how long visitors stay on the site, and what devices they use. We use this data to identify changes that we could make to improve your experience and make our website more efficient.
Marketing Cookies
We set some cookies so you are shown more relevant marketing content. These include cookies from third-party advertising networks to show you different adverts on their services if you have previously visited our site. If you choose not to allow these cookies, you may experience less relevant advertising on other sites.
Browse Documentation

Querying composer fields

Created by m.summerfield on 18 Nov 2021

Composers are typically used by editors to create body in content types such as blogs. It's not unusual to see 30+ fields used for some body content and some of these may be components, which in turn have multiple fields.

Ideally we need to keep this number to be less than 1,000 so that it doesn't affect search performance. To do this, composer fields are mapped as a flattened type which means you can still use certain operators but without the need to map each field.

In general, you should not use composer fields for data that you filter on to produce searches or listings. It is preferable to use components and/or repeating fields where you want to store repeated or structured data that you will then filter on. You can of course search all the content of a composer (and other text fields) using the searchContent field.

In v14 you can still search all the items in the composer field using the following search operators:

  • contains
  • startsWith
  • endsWith
  • between