Jonas Bergqvist
Sep 25, 2024
  1907
(0 votes)

Required fields support in Optimizely Graph

It's been possible to have "required" properties (value must be entered) in the CMS for a long time. The required metadata haven't been reflected in Graph - until now. Its now possible to get the GraphQL schema updated, to get information about which fields that always has a value.

Configure CMS

The CMS must be configured to send metadata about required (value must be entered) properties to the GraphQL schema. We had to add this configuration setting, to not create a breaking change for the 3.11.0 release. The default value is 'false'.

Set property as required

Here is an example of the property "Heading" in the "TeaserBlock" content type. This property is set to be "required" (value must be entered).

GraphQL query with required support

The GraphQL query is now configured to know that the field always has a value

Sep 25, 2024

Comments

Please login to comment.
Latest blogs
Pushing Content Between Optimizely DXP Environments

We've been working with a client who has been on Optimizely 11 for a long time - self-hosted, on their own server infrastructure, with a content...

Matt Pallatt | Jun 2, 2026

Launching “Learning by Doing – Optimizely OPAL Series” | Episode 01 is Live!

  Introduction With Optimizely OPAL, we’re seeing a shift from "content management" to "intelligent content orchestration". But here’s the reality ...

Ratish | Jun 1, 2026 |

Finding Thomas Part 2 - The Recognition Engine

Remember Thomas? In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard...

Ritu Madan | Jun 1, 2026

Unleashing Cloudflare's Power: Setting up Orange-to-Orange (O2O) with Optimizely DXP

If you're working with Optimizely DXP, you're probably already aware that it uses Cloudflare under the hood to deliver performance and security to...

David Drouin-Prince | May 30, 2026 |