Knowledge article throws error when the language of the user is different than the language of the knowledge article
Last updated 2 days ago ·Reference W-7341014 ·Reported By 10 users
In Review
Summary
Knowledge article throws an error when the language of the user is different than the language of the knowledge article. This happens in Salesforce Lightning.
Repro
SetUp: Sign up a local org
- Enable Knowledge in org.
- Enable knowledge for admin/test user(and make sure Language defaults to English).
- Enable Lightning Knowledge.
- Enable feed tracking for Knowledge from Setup.
- Enable multiple language support
- Add “Dutch” (or another) language and make it active. (Now you have 2 active languages - English (Default) and Dutch)
- Create a new user “Test User” (with ‘Standard User’ or ‘Standard Platform user’ or any other profile)
- Enable knowledge for this user (from User Details page).
- Set the local language for user to Dutch (or other added language)
- Edit the knowledge page layout and add “Language” field to the layout for all profile.
- Create a new knowledge article with language “English”.
- Publish the article.
- Once the article is published then ‘at mention’ the ‘Test User’ you created above in comments at the published chatter post.
Login as the new User you created above (i.e. ‘Test User’):
- Look at the chatter notification at the top of the page.
- Click on the chatter notification and once opened then click on the title of the article to open the article.
Result: Error: We couldn't find the record you're trying to access. It may have been deleted by another user, or there may have been a system error. Ask your administrator for help.
- Now try opening the article after navigating to knowledge tab and the article open fine.
Workaround
Go to the knowledge article directly or follow the chatter thread in Salesforce Classic
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.
