Hello,
in our company we use Person.UID_DialogCulture as the primary display language in both our Angular web application and the old Webportal (since the Webportal overwrites the browser culture if person culture is set).
We have many API endpoints in the Composition API created with the `FromTable()` method especially in order to enable the lucene index search on translated columns. Unfortunately, the search that is invoked by the Composition API automatically uses the Browser Culture for the lucene search query. Hence a Person which for example has EN as his primary browser culture but Person.UID_DialogCulture = QBM-CULT-de-DE is not able to get a proper result as the user expects to search for a german term but the lucene search query searches in the english dictionary behind the scenes.
Is there any way to work around this behavior?
