Errors with moving custom table and record producer update set

[rrao]

Having issues with updates sets for custom table and record producer. Moved the update sets to TEST instance. After committing the update sets, I cannot see the complete custom table and record producer. Backing out is not working. Running into backout errors even though previewed the current and previous records and clicked to restore the previous records. Any advice or options is appreciated.  Thanks.

[Nayan ArchX]

Hi, 

🧠 Why this happened

When you migrate:

• Custom table

• Record Producer

• Variables / Variable Sets

• Client scripts / UI policies

• Dictionary entries

ServiceNow actually creates dozens of records behind the scenes: (such as, but not limited, depend on your scenario)

• sys_db_object (table)

• sys_dictionary (fields)

• sc_cat_item_producer

• item_option_new

• item_option_mtom

• ACLs

• UI policies

• Client scripts

Update Sets often:

❌miss dictionary children
❌miss variable mappings
❌commit in wrong order
❌partially apply schema

So in TEST you end up with:

• Table exists but missing fields

• Producer exists but broken

• Variables missing

• Backout fails because DDL changes can’t be reversed

That is your symptom? 

If my response has resolved your query, please consider giving it a thumbs up ‌‌ and marking it as the correct answer‌‌!

Thanks

Nayan Patel

IT ServiceNow Consult, ServiceNow ArchX

If my response has resolved your query, please mark it Helpful by giving it a thumbs up and Accept the Solution

[rrao]

Yes, that is exactly what has happened in TEST. Please advise on how to resolve it. Thanks.

[Nayan ArchX]

Hi, 

Happy to help you. 

You may try this

⭐ OPTION 1 (FASTEST): Delete + Re-deploy clean

Recommended if TEST data doesn’t matter.

Steps:

A. Delete broken artifacts

In TEST:

1. Delete Record Producer

2. Delete Variable Sets / Variables

3. Delete Custom Table

Then: System Definition → Tables → Delete

B. Re-import Update Set

But this time:

1. Preview

2. Resolve ALL missing dependencies

3. Commit

C. Validate:

• Table

• Fields

• Producer

• Variables

OPTION 2 (as Enterprise-safe): XML export from DEV

If deletion isn’t allowed:

From DEV:

Right-click each:

• Table

• Producer

• Variables

Export as XML.

Then import XML into TEST.

This bypasses Update Set dependency issues.

If my response has resolved your query, please consider giving it a thumbs up ‌‌ and marking it as the correct answer‌‌!

Thanks

Nayan Patel

IT ServiceNow Consult, ServiceNow ArchX

If my response has resolved your query, please mark it Helpful by giving it a thumbs up and Accept the Solution

[rrao]

Many Thanks for the solution. I am going to try and let you know if it worked. Thanks,