How to Retain Relationship between KB Article with Versioning and Custom Table

[Debby Shea Ande]

My company uses the Knowledge module with the Knowledge Management - Advanced plugin installed. This plugin enables versioning among other features.

We use three custom knowledge article templates in addition to the OOB templates.

We have created a basic custom table. We need to be able to show the custom table as a related list in the back-end form of our knowledge articles.

The issue I am running into has to do with versioning. I set up the Related List, and am able to associate a record in the custom table with a knowledge article. This works as expected. However, if the article is checked out, edited and republished, the item from the custom table is no longer displayed in the Related List for that article.

I’ve looked over the table schema for knowledge but admit I’m not able to figure out how to configure the relationship correctly. The goal is to keep the related list entries for each knowledge article persistent from version to version. Thanks!

[bammar]

Does the republished article have a new sys_id aka is it a new record? Related lists pt to specific records which they reference, 

You may have to create a RELATIONSHIP which will be a related list but is more dynamic in terms of where it will appear - OR n the new custom table instead of referencing a KB- make a list collector field so that the custom record can reference all versions( assuming each version creates a new record)

[Debby Shea Ande]

The republished article has the same article_id from version to version. The sys_id is a field in the table, but I'm having difficulty surfacing it as the list view and form views don't display it as selectable. I will continue to dig into this to determine whether it changes.

If you could point me to documentation about how to create the relationship, as you discussed above, I would greatly appreciate it.

[Debby Shea Ande · Accepted solution]

I was able to successfully create a many-to-many relationship table between the knowledge table to the custom table, and to point to the article_id field. This was successful in retaining the relationship from version to version.

[Amritha1]

Hello There, Could you please let me know how this was achieved? I'm having similar usecase and would like to try this solution.
Thanks in advance!