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:
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?
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?