Jonas Bergqvist
Sep 25, 2024
visibility 2245
star star star star star
(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

error Please login to comment.
Latest blogs
Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |

Giving Optimizely 13 Content Types Meaningful Icons and Thumbnails

When working with an Optimizely CMS solution that has evolved over time, it is common to end up with many content types. As the number grows, the...

Pär Wissmark | Sep 16, 2026 |

force-dynamic vs connection() for Optimizely Graph

If you have built an Optimizely CMS SDK site, you already know getContentByPath on a catch-all. This post is about the part that file never says ou...

Chirag Khanna | Sep 16, 2026 |

I built a thing - nOSC & nOCP - an experiment?

I don't think I'm always that convensional . And that's where this starts... So firstly, I was lucky enough to see OCP UI extensions for Optimizey...

Matt Pallatt | Sep 15, 2026