Decision record with name "fulfillment Table delta" already exists

[learn nv]

Hi All

I am receiving below alert and decision table is keep on loading when I tried to input the data by clicking on 'create draft' option on decision table.

Alert: Decision record with name "fulfillment Table delta" already exists

Could you please suggest the solution.

[MatheusS6223994]

Just delete the delta version of the decision table from  sys_decision_delta table. Delta version is a draft version created when um click on 'Draft' button in the Decision table. After deleting it, you can click again in Draft button.

[learn nv]

Hi Matheus, 

I am facing this issue in TEST and not having any issues in DEV. I am worried what if this issue occurs in PROD?  as we are looking to deploy to PROD.

[Ankur Bawiskar]

@learn nv 

there are challenges when it comes to migration of decision table

As a backup please ensure you keep manual activities ready for the same.

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

[learn nv]

Hi Ankur,

Thank you for your reply and could you please suggest on below.

1. is it better to export and import the the decision table data using export and import option or individuals should capture the decision table data in respective update sets while doing the development.

2. Any system property changes required if we need to add more than 20 rows to a decision table?

[MuhammadUmair]

I’m also currently facing an issue in the Dev instance where I’m unable to edit Decision Table entries after clicking on "Create Draft". Additionally, when I delete the delta version from the sys_decision table and try to create a draft again, the system generates a new delta version, but the same error still occurs when clicking "Create Draft".

I’ve searched through the documentation but haven’t found anything that clearly explains the behavior of delta versions in Decision Tables — such as why they're created, how they work, and how we can avoid or manage issues like this.

After some investigation, I decided to inactivate the current Decision Table and create a new one to continue working. However, I’d really appreciate it if anyone from the community  or from the ServiceNow Support team could help clarify the expected behavior here or share any relevant documentation.