Unable to capture decision table inputs, conditions, results.

[SiripriyaP]

I have created a decision table , and captured in the update set. while retrieving, there were no errors. but when I open decision table in the other instance and check there is a table but not the inputs, conditions and the result

[Deepak Shaerma]

hi @SiripriyaP 

this is the common issue with decision tables, my suggestion is to create a new update set and copy the decision manually(means try to create a new one). then move the update set to another instance and check.

Happy to help! ‌‌
To help others in the community find this solution, kindly mark this response as the Correct Answer ‌‌ and Helpful‌‌.
Warm Regards,
Deepak Sharma
Community Rising Star 2025

[Mohit 101]

hi @SiripriyaP ,

Modified during your session. The main record in sys_decision might move, but the actual logic (inputs, conditions, and results) stays behind.
To fix this, you can use one of these methods:
Force Capture (Recommended):
Open the Decision Table in your source instance.
Change a minor detail (like the description), Save, then change it back and Save again.
Ensure the table is in a Published state; this often triggers a capture of all related artifacts (inputs, rules, results) into your current update set.
XML Export/Import (Quickest Bypass):
If the update set keeps failing to grab everything, manually export the following as XML from your source and import them into the target:
Inputs: sys_decision_input
Conditions: sn_decision_table_decision_condition
Answers: sys_decision_multi_result or related result tables.
Check Application Scope:
Verify that your Update Set and the Decision Table are in the same application scope. Cross-scope updates sometimes fail to capture related records properly.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for.

Thank You

[Aditya_hublikar]

Hello @SiripriyaP ,

yes sometime might it happen .I thinks you should create new decision table and captured it then move again. 

If this helps you then mark it as helpful and accept as solution.

Regards,

Aditya

[Ankur Bawiskar]

@SiripriyaP 

We have seen sometimes similar error.

The only way we achieved was to re-capture again in update set and migrate

members have raised similar question earlier, worth checking below links

Issues While Moving Decision Table Update Set from One Instance to Another

ServiceNow Decision Table - Issues with moving desision table data fron Dev instance to Test Instanc  

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏