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

[Shashank_Jain]

Hello all,

I’m trying to move a decision table created in the Dev instance to the Test instance. I created the entire decision table from scratch and ensured each update was captured in the update set. While moving the update set, there were no preview errors. However, after committing the update set, if we go to the decision table it shows like this :

Please refer the screenshot below :

Can anyone share any best practices for moving decision tables and subflows between instances?

Thanks in Advance!

[G Ponsekar]

@Shashank_Jain ,

Sometimes, caching in the target instance can prevent the newly committed changes from being immediately visible.

• Resolution: Clear the cache in the target instance by typing cache.do in the navigation filter and pressing Enter. click clear cache link

If I could help you with your Query then, please hit the Thumb Icon and mark as Correct !!

Thanks, GP

[Ankur Bawiskar]

@Shashank_Jain 

We have seen sometimes similar error.

The only way we achieved was to re-capture again.

Migration via Update set is the best practice for decision table and subflows.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Bhimashankar H]

HI @Shashank_Jain ,

Make sure you have same application scope as the update set. or else go table 'sys_decision' open your decision table and there would be 'add to update set' option in related link, once added check in update set created by system automatically as parent update set. Decision table should be in published state.

The entry in customer update set should have all the rows from decision table. It will have similar pattern. Refer the screenshot.

Thanks,
Bhimashankar H

-------------------------------------------------------------------------------------------------
If my response points you in the right directions, please consider marking it as 'Helpful' & 'Correct'. Thanks!

[Shashank_Jain]

Thank you all for the responses!

I just migrated the update set again, and the decision table looks fine now.

I’m still trying to understand why the ServiceNow instance shows these kinds of issues when migrating decision table, flows and subflows. 

Is this a problem from servicenow side ?