Hi Binh,

Can you expand on what you mean by "...by adding properties within IContentApiModelProperty" ? How are you adding these properties?

You can mark any property on the content type as searchable.

Note, Optimizely Graph supports fuzzy search for string fields and you enable it within the query for the supported operators. Refer to developer documentation for usage and examples

Hi Ronil,

Thanks for your feedback. My properties are calculated properties. So I do not want to add them to content type as normal properties. I added custom properties to Graph model as same as this link https://blog.ynzen.com/how-to-add-a-custom-property-in-optimizely-graph

I'm not sure how to mark custom (calculated) properties but string properties are marked searchable by default. Have you tried a fuzzy search on your custom property?

A possible workaround could be, assuming you are using Optimizely Graph in a PaaS setup, to add them as normal properties so they are searchable but hidden from edit view. 

E.g.

[ScaffoldColumn(false)]
public virtual string CalculatedProperty { get; set; }

Then you can still use your IContentApiModelProperty implementation to override the normal property with your calculated logic (by using the same property name).

HI Ronil,

Yes, I see about the workaround. But it still does not help in case such as I want to use extended properties for searching all IContent data, not for a specific content type. So this workaround just works if I do search for a specific content type, not for general search.

I also saw in the code base and see that not all string properties are marked searchable by default. The properties are marked searchable if they have annotation [Searchable] or the system properties such as Name