Employee Center: Child Topics not being shown in dropdown, when language is translated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
In the employee center, when language is English, the main topics and its child topics are shown as expected.
But once language is switched to e.g.: Arabic, (all the topics are translated and available in translated text), only the main topic is shown and drop down does not show any child topics.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi @MarakkarHc
Even if translations are populated in the sys_translated_text table, Employee Center automatically hides child topics in dropdowns if certain criteria aren't met under the translated language context.
Here are the three most common reasons and fixes:
- Missing Connected Content (Most Common): The mega menu hides topics that have no visible connected items (Catalog Items, Articles). If your linked content is only available in English or restricted by language-specific User Criteria, the child topics will disappear for Arabic users. Ensure at least one linked item is active and visible in Arabic.
- Portal Node Caching: Taxonomy layouts are heavily cached. Switching languages in a single session often fails to re-render deep sub-menus. Test this by clearing your instance cache (cache.do) and using a clean Incognito window.
- AI Search Indexing: If your dropdown relies on AI Search data sources, the newly translated taxonomy paths might not be indexed yet. Go to your AI Search Indexed Sources and trigger a re-index for your taxonomy.
Quick Test: Link a universally accessible Catalog Item directly to one missing child topic. If it appears in the Arabic dropdown, it confirms you have a content visibility issue.
Hope this helps! Please consider marking this as Helpful or Accept as Solution if it resolves your issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
The missing child topic has a universally accessible catalog item linked. (Only not accessible to snc_external)
It still does not appear when translated to Arabic.
The catalog item is translated and available in the translated text
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
31m ago
Thank you for confirming that both the item and the translation records are properly configured. This rules out the content emptiness rule and narrows it down to localized user constraints or taxonomy tree evaluation bugs.
Since the item is translated but the child topic is still hidden when switching to Arabic, inspect these three specific technical layers to pinpoint the issue:
- Language-Specific User Criteria (Available For / Not Available For)
Even if the item is accessible in English, check the User Criteria records mapped to that specific Catalog Item.
- The Culprit: If you have custom User Criteria targeting specific language preferences, locations, or organizational fields that change when an Arabic profile is evaluated, it will render the item invisible to that active session.
- The Fix: Explicitly double-check the Available For-related list on the Catalog Item record. Test by impersonating an Arabic user who still retains full standard corporate system roles.
- Advanced Portal Navigation Hierarchy Sync
If you are utilizing Advanced Portal Navigation widgets on your Employee Center instance:
- The Culprit: The mega menu configuration caches the multi-level structural nodes. If you have added translations after linking the items, the multi-language structural path maps often fail to bind dynamically without an explicit structural refresh.
- The Fix: Navigate to All > Advanced Portal Navigation. Open your primary Employee Center Navigation record. In the Menu Items related list, click the Sync Hierarchy button.
- Clear Taxonomy Node Cache (cache.do)
Employee Center taxonomy trees are some of the most heavily cached application entities in Next Experience portals.
- The Culprit: When a translation record is added directly to sys_translated_text, the localized node properties do not always invalidate the active instance node memory pool immediately.
- The Fix: Elevate your privileges to security_admin, type cache.do into the application navigator to flush the node cache and test the Arabic portal exclusively using a completely fresh Incognito/Private browsing window.
I recommend triggering the Sync Hierarchy button first, followed by a node cache flush, as that combination handles most outstanding multi-language menu drop-down issues.
Hope this helps track down the visibility break! Please consider marking this as Helpful or Accept as Solution if it resolves your issue.
Other Refrences:
