Updating Topic Category for Topic Details

[robbieflink]

Hello! In our environment, we have accidentally created three Topic Categories for the same purpose, and have some Topic Details split out amongst them. We are wondering if there would be any potential fallout from updating the Topic Details to be aligned under one common Topic Category for the purpose, so that we could remove the duplicates. We have one Topic Category with 19 Topic Details, one Topic Category with one Topic Detail, and the last Topic Category with one Topic Detail. We are looking to have only one Topic Category with all 21 Topic Details, and to remove the 2, then unused, Topic Details.

Are there any specific considerations to be made before attempting this?

[Sandeep Rajput]

@robbieflink Before making this change make sure to look for the HR Services which are going to get impacted by this change. Once done, you can update the Topic category and Topic details and update the imapcted HR Services according to the new hierarchy. 

[RaghavSh]

If this question is related to taxonomies, this should only impact the front end, if you move the topic details across to the one with 19, it should not impact anything at backend.

Its just the look and feel change for user.

[RaghavSh]

@robbieflink Were you able to get this working

[M Iftikhar · Accepted solution]

@robbieflink , 

If this is related to HR Services on the backend, you’ll want to check which COE (Center of Excellence) each Topic Category belongs to. Sometimes different Topic Categories can have the same name, but what actually makes them unique is the table (COE) they’re associated with.

• If all your Topic Categories belong to the same COE, then you should be safe to consolidate. The usual approach would be:

  1. Link the HR Services to the one Topic Category you want to keep.

  2. Mark the duplicate Topic Categories inactive first and validate that everything still works as expected.

  3. Once confirmed, you can delete the unused Topic Categories.

If you’re talking about Taxonomy (the front-end side), then it’s more flexible;  you can link a Catalog Item to any Topic without impacting the backend logic.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.