Virtual Agent updates not captured in Update Set

[Luiz Lucena]

Hello everyone, 

I've been working on Virtual Agent for few months, all in our DEV instance and I gonna have to clone PRD over DEV this Friday, so I saved the update sets I've been working on and moved to a temporary instance to capture what's gonna happen.

For one update set with 444 customer updates, I've got 22 errors. The majority for sys_cb_design_topic table.

So, a new topic is not captured in an update set? 

Anyone got any tip working and moving update sets for Virtual Agent?

Thanks in advance!

[Mark Roethof]

Hi there,

"So, a new topic is not captured in an update set?"

This is not correct. New topics are captured in update sets. Have you verified the customer updates on your dev instance for example? Was the customer update stored in the correct update set? Can you find the customer update at all?

Anyway, new topics are captured in update sets.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

[Luiz Lucena]

Yes, I've checked that and they are showing as published in the correct update set.
Even they showing in the update set, the target instance presents this:

Could not find a record in sys_cb_topic for column cb_topic_id referenced in this update, but did find it in another uncommitted update set

So, I checked the other update set, and could not find the remote update in the other one.

One of the update sets are presenting around 80 like this one:

Cannot commit Update Set 'LL - Virtual Agent Initial Setup 2' because: Update scope id '134450a0b3781300787162ac16a8dc1e' is different than update set scope id 'global'. Resolve the problem before committing.

I think this one is because while working on 'global' I had to edit something that belongs to other application scope.

[Ankur Bawiskar]

Hi,

seems you are having the wrong component in wrong application scope.

Regards
Ankur

[Luiz Lucena]

Yup.

I believe that could be because the update sets were saved in Orlando and was promoted to an instance in Quebec, could that be the case?

[Mark Roethof]

No, also in Orlando Virtual Agent topics are stored in Update Sets perfectly fine.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020, 2021 ServiceNow Community MVP
2020, 2021 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list