Unable to get Decision Table inputs and conditions to be captured in Update Set

[kdelbridge]

I am having a difficult time getting my Decision table inputs and conditions to be captured in an update set. Trying to get this pushed from DEV to TEST to ensure catalog item and flow are working as expected, but can't accomplish testing without all components of Decision Table.

I did create another update set in DEV, went to the Decision  Table and made some small edits  and saved again, so I could capture this in an update set and still not working. 

I can see the Decision table in TEST, but the inputs and conditions are blank.

I appreciate any assistance anyone can offer.

[shloke04]

Hi @kdelbridge ,

Ideally OOTB both Decision table input and condition should get captured in an update set the way you have mentioned and have tried at my end and can see it does gets captured and I do not see issue during migration to higher environments.

In case if this is causing trouble at your end, you can follow one of the options listed below which you are comfortable with:

Option 1:

1. Decision Input: Decision Inputs are stored in a table named "Decision Inputs (sys_decision_input)". 

2. Navigate to this table and search for table column contains "Sys id of your Decision table". This will give you all the inputs which you have created against that decision table.

3. OR alternatively you can search for individual column name as well using the "column name" attribute available.

4. Open the individual record, make some changes like Active True to False and then back to True and recapture it and then move it to higher environments.

Have attached a screenshot below for reference:

Decision Table Conditions: These are stored in the table named "Decision Conditions (sn_decision_table_decision_condition)".

Repeat the above steps as mentioned for Decision Inputs.

Option 2:

1. Navigate to both Decision Input and Condition table.

2. Filter the records which you want to migrate.

3. Export as an XML

4. Navigate to target instance

5. Retrieved Update Set

6. Import as an XML