Making changes to a type using Optimizely.Graph.Source.Sdk (in CMS13) - change not picked up when querying

I'm using Optimizely.Graph.Source.Sdk and GraphSourceClient.Create(graphOptions.GatewayAddress, "mysrc", graphOptions.AppKey, graphOptions.Secret);

I have a custom type, MyCustomSearchDocument, it's not a CMS content type just a very simple flat class.

It's working fine. But I want to add another property to it, it's a List<string> if that matters.

I add it, use it with ConfigureContentType using .Field(x => x.MyNewListProp, IndexingType.Searchable) and then SaveTypesAsync without errors.

Looks like it is in the schema and also as a SearchableStringFilterInput but queries still fail.

Am I missing some step when changing the type structure or can I clear the source better before indexing?

"errors": [
    {
      "message": "Field \"MyNewListProp\" is not defined by type \"MyCustomSearchDocument\". Did you mean \"MyNewProp\"?",
      "locations": [
        {
          "line": 15,
          "column": 11
        }
      ]
    },
    {
      "message": "Cannot query field \"MyNewListProp\" on type \"MyCustomSearchDocument\". Did you mean \"MyNewProp\"?",
      "locations": [
        {
          "line": 26,
          "column": 7
        }
      ]
    },
    {
      "message": "Cannot query field \"MyNewListProp\" on type \"MyCustomSearchDocument\". Did you mean \"MyNewProp\"?",
      "locations": [
        {
          "line": 34,
          "column": 7
        }
      ]
    }
],
#343693
Edited, Oct 28, 2026 8:33
Vote:

Solution for now was to go outside of the SDK and use API endpoints directly to clean up before adding updated types.

I separated content and types to see if anyone failed:

  • /api/content/v3/sources?id=mysrc&mode=data&slot=
  • /api/content/v3/sources?id=mysrc&mode=types&slot=
#343699
Edited, Oct 28, 2026 10:38
Mardy

Hi Johan,

I tried reproducing this in my CMS 13 Alloy sample using

"Optimizely.Graph.Source.Sdk.SourceConfiguration.Optimizely.Graph.Source.Sdk" version "2.0.1"

I registered a custom type, then added a new "List<string> property" using ConfigureContentType with "IndexingType.Searchable" and called "SaveTypesAsync()".

I didn't perform any content indexing or call "SaveContentAsync()" after updating the type. The new property appeared in the GraphQL schema, and I could query and filter on it successfully.

I couldn't reproduce the issue. Which version of the Source SDK are you using? Also, does the new property appear in both "MyCustomSearchDocument" and "MyCustomSearchDocumentWhereInput" when you inspect the GraphQL schema?

#343700
Oct 28, 2026 10:45
Johan Kronberg - Oct 29, 2026 9:20
Optimizely.Graph.AspNetCore" Version="13.4.1"
Optimizely.Graph.Cms" Version="13.4.1"
Optimizely.Graph.Cms.Query" Version="13.4.1"
Optimizely.Graph.Source.Sdk" Version="2.0.1"

I think I made earlier changes this way too without needing to clear data and types. Schema looks correct, query autocomplete in GraphiQL looks correct but still query fails like in first post.
Mardy

That is an interesting workarund, did you try cleaning only the types (mode= types) before registering them again, or clearing both data and types resolved the issue?

#343701
Oct 28, 2026 10:55
Johan Kronberg - Oct 29, 2026 9:18
I only tested first clearing data and then types.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.