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!

[Luiz Lucena]

So the promoting the update set to an instance in another family version should not cause that, right?

EDIT: Think I'm getting close.

While working in Global scope, some records were updated using the "To edit this record click here."
So, those records belongs to another application.

Now, I created another update set under the original application and I'm moving the updated records to that original application and hope that works.

But still couldn't figure out why some records could not be found, maybe they were deleted during development.

[Mark Roethof]

"So the promoting the update set to an instance in another family version should not cause that, right?"

That should indeed also not be an issue.

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

[Ankur Bawiskar]

@Luiz Lucena 

Usually there should be an entry into that table for the topic once you publish it and it should get captured in update set.

There could be multiple reasons for that update not getting captured.

But simple way is to re-publish the topic again in fresh update set and move it to next instance.

Regards
Ankur

[Luiz Lucena]

Hi Ankur,

Trying that.
EDIT: I'm afraid will get the same results, because the customer update is being shown as part of the update set being moved.