• State Not Answered
  • Replies 3 replies
  • Subscribers 95 subscribers
  • Views 880 views
  • Users 0 members are here
Options
Related

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

daniel.storck
over 3 years ago

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.

Parents Reply Children
  • 0 over 3 years ago in reply to Hanno Bunjes

    Hello Hanno,

    we are using the "search" parameter that is supported for an endpoint if its implemented by the HandleGetByQuery-Method of the Composition-API. We are returning certain columns in our response as well as one column with EntryKeys which are going to be translated client-side. But since this column contains descriptions, we'd like to be able to search within that descriptions during the invocation of the api method as well.

  • 0 over 3 years ago in reply to daniel.storck

    Hello Daniel,

    It sounds like the translations are not picked up by the indexer. Is the "EntryKey" column configured as a multi-language column in the model? If not, the indexer has no way of knowing that the column contains multi-language data.

    Hanno