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

[Swapna Patiband]

Hello,

We are facing issues when moving decision table data from Dev to Test.

1. Decision table is already moved to Test

2. When new requirements are added we are capturing new added rows in update set and retrieving/committing in Test.

3. After committing  new records are not added in Decision table in Test. This is the issue.

4. Many developers are working on same decision table, looks like it's overwriting when update sets are moved to test.

Please help in migrating this correctly to differently instances. Any other specific steps while capturing decision table data.

Thanks,

Swapna.

[Murthy Ch]

@Swapna Patiband 

We have also faced similar issues while working on DT.

Make sure to capture all updates because when you add any row (or) delete any row it creates lot of files and all of those files are needed to make DT work.

These are the files you always need to consider when working on DT's:
sys_decision_input

sn_decision_table_decision_condition

sys_decision

sys_decision_multi_result

sys_decision_multi_result_element

sys_metadat_link

sys_documentation

Hope this helps

[Swapna Patiband]

Thank you!!

[jonokoster]

I found an other table to add to the list:

sys_variable_value