Adding Topic to Catalog Item not Captured in Update Set (Employee Center)

Marcus Walbridg
Tera Expert

We previously were using categories for the old portal.  When one adds a category to a catalog item, this change is captured in an update set.

 

On a catalog item, there is a related list called ‘assigned topics’.  This is the relationship between the catalog item and the topic, similar to connecting a catalog to a category.  The change of adding a topic to a catalog item is not captured via update set though.

 

Some context, we have a group of people that make catalog items/flows outside the admins.  They capture their changes in Dev via update set, and promote them to Production through us admins.  Now that they can’t capture adding a topic to a catalog (explained above), we have an issue on our hands. 

 

Curious to see if anyone in the community has encountered this, or if there are any solutions

6 REPLIES 6

Mark Roethof
Tera Patron
Tera Patron

Hi there,

 

It's correct that this is not captured in an update set. It is considered data.

 

While for Catalog Items you could do this on DEV and move it up to higher environments, doing the same for Knowledge Articles won't be possible (since you do write Knowledge Articles on PRD).
You might push the Connected Content into an Update Set or export it to XML and import it.

 

Kind regards,
Mark

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

Hey Mark,

 

Thanks for the fast response.  I can see why you'd say it is data, but conceptually it seems the same as categories to me.  Connecting a catalog to a category is captured, but to a topic is not.  Is it possible to get them to capture just like categories?  Ideally we do not want to add any more steps to the current process.

Agree with you so we get catalog item creation captured in update set; and when going to production we don't get the items in the topics because that relation itself is data ? That's non sense to me.

Has anyone tried creating a case for this ? Would ServiceNow reply this is "expected" and "by design" ?