Knowledge article sys id is getting change on each update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2022 09:24 AM
Hi Experts,
Knowledge article sys id is getting change on each update , when using the hard coded KB link it is showing the older version of the Knowledge Article.
e.g. - https://<ServiceNow>?id=kb_article&sys_id=<sysID>
Is there any way to get the correct/latest KB link even on each update ?
- Labels:
-
Scripting and Coding
-
Team Development

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2022 10:21 AM
Last I checked perma links where is the format of
https://<instance>.service-now.com/kb_view.do?sysparm_article=KB0011146
The reason the sys_id changes is because versioning is installed and in use so any update to a published article causes a new one to be created.
If you are looking for a link that takes you to the platform interface I don't know of one that will take you to the latest version automatically. You should get a message at the top of the form that tells you there is a newer version and a link to go there.
Someone at some point customized our Service Portal so I don't know if there is a perma link that will get you something other than the OOB knowledge portal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2022 01:16 AM
Hi ,
Thanks for your response.
Permalink is redirecting to some other view , need it in Service Portal view only.
Can you please suggest ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2022 10:31 AM
When looking at a KBA using your Service Portal there should be a link that says "Permanent Link" that you can click to get what it is for that portal.
At a guess its probably something like
https://<instance>.service-now.com/<portal_name>?id=kb_view.do&sysparm_article=KB0011146
but I don't know for sure because someone modified our pages for this were modified and that functionality appears to have been removed.