- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2023 11:04 AM
Hi,
We've enabled AI search on our instance, and the typo handling works great when the user's language is English. However our portal is available in Norwegian and Brazilian Portugese also. When user changes to one of those languages, typo handling does not work at all, example:
Portal in English
Desired outcome: Search term "projec" results in suggestion "project"
Actual outcome: Search term "projec" results in suggestion "project"
Portal in Norwegian
Desired outcome: Search term "projec" results in suggestion "project"
Actual outcome: Search term "projec" results in no matches
I know typo handling is not supported in Norwegian or Brazilian Portugese and that's ok. Most of our portal content is globally available in English, but the portal itself is available in those languages.
What we want: If user has portal enabled in Norwegian or Brazilian Portugese and searches for a term, the typo handling defaults to English. Does anyone know how to achieve this?
Thanks!
Solved! Go to Solution.
- Labels:
-
AI Search
-
Search
-
Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2023 07:38 AM
Hi,
This is a good question, however currently the global fallback in not used specifically for the autocorrect functionality when the portal language is outside the list of supported languages. Adding this capability to the idea portal would be a great idea.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2023 07:38 AM
Hi,
This is a good question, however currently the global fallback in not used specifically for the autocorrect functionality when the portal language is outside the list of supported languages. Adding this capability to the idea portal would be a great idea.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2025 02:31 AM
Did you ever find a way to do this? I'm currently setting up AI Search for our Employee Center and have hit this exact problem. (after finding out that AI Search didn't work for our users with Danish language chosen, but there is a system property for that)