Does Approximate Match Search Work on Computed Fields?

Data Services
1

Hi!

It seems like the Approximate Match Search does not work on Computed String Fields. Am I right in my assumption?

Thanks in advance

2

Hi @karin-sparse-tundra ,

Approximate match filters work on all string fields that are not transient. Computed fields are included in the search results for such filters.

3

Thank you very much for your clarification. Then the problem was that the field was transient and not the computation itself. I will keep that in mind for the future.
Is there any workaround to get it to work for transient fields?

4

Hi @karin-sparse-tundra,
I found the following in the Data Services documentation:
mgmtp.a12.dataservices.documents.validation.persistTransientFields

The following remark is made:

This property allows overriding documents persistence to persist transient fields. The default state in v34.0.0 will be not to persist transient fields.

I’m a BA and therefore not an expert in the topic, so I’m not sure if this is the workaround that you were looking for. I would also tend to ask the question, why do you need the field to be transient? Is the workaround to model this field normally, i.e. not transient?

5

Transient fields are meant for UI use-cases where you want to have some control dependent on a calculated value but you do not want to persist it. As Malcolm mentioned, there is a possibility to overwrite this behavior on the DS side and we will persist transient fields and therefore it will be possible to search for them. However, this is not something I can recommend. My recommendation would be to not search for transient fields. This means either not mark fields as transient or mark them as transient but query on different fields.