Handling of translations in HTML5 application and Composition API in respect to AppServer search

Hello,

given the following situation: The Composition API returns some columns including one column that contains an EntryKey for a MultiLanguage description. The EntryKey is being used within a HTML5 application and translated on application's side by using the translation pipe. In addition, that description should also be searchable via utilizing the AppServer search. Unfortunately, using the search parameter in the request, only the EntryKey is considered but not the actual translation behind. So for instance:

EntryKey = 123, EntryValue(EN) = "One two three", EntryValue(DE) = "Eins, Zwei, Drei"

Search: 1 => API returns the object

Search: One => No result

Search: Eins => No result

How can we handle such a situation without handling the translation on both API & Client side? Can the AppServer be instructed to consider the actual translation of an EntryKey instead of the EntryKey itself?

Thanks, best regards.