Notifications

158 views

Description

During List Edit / Inside Embedded Lists changing the value of a dropdown always sets its dependent to -- None -- even if the same value is present.

Steps to Reproduce

For embedded lists:
 
1. Create a custom table called u_test_table.
2. Create two string fields: u_category and u_subcategory.
3. Add two choices for u_category: Category1 and Category2
4. Set category1 as the default value of u_Category.
5. Add thee choices for u_subcategory:
- value = 100 , dependent value = category1
- value = 100 , dependent value = category2
- value = 200 , dependent value = category2
 
Set the default value of u_subcategory to 100.
 
6. Create a reference field called u_incident and refer to the incident table.
7. Go to the incident form, right-click in the form header, and choose Configure > Form Layout.
8. Add "u_test_table" as an embedded list on the form.
9. Open the incident.do form and double-click on the category.
Note that "category1" and "100" is selected.
9. Change the first dropdown to "Category2".

Instead of the value in Subcategory dropdown remaining "100", the value becomes " -- None --".

For List View (v2)]:
 
1. Create a custom table called u_test_table.
2. Create two string fields: u_category and u_subcategory.
3. Add two choices for u_category: Category1 and Category2.
4. Set category1 as the default value of u_Category.
5. Add three choices for u_subcategory:
- value = 100 , dependent value = category1
- value = 100 , dependent value = category2
- value = 200 , dependent value = category2
 
Set the default value of u_subcategory to 100.
 
6. Open u_test_table.do and create a new record with category set to "category1" and subcategory set to "100".
7. Go to u_test_table_list.do and double-click on the Category field then change the dropdown to "category2".

Instead of the value in Subcategory dropdown remaining "100", the value becomes " -- None --".

Note: If the same record is opened on a form this works as expected.

Workaround

After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Customer Support.


Related Problem: PRB1238493

Seen In

Istanbul Patch 6
Jakarta Patch 4

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-07-19 04:39:55
Published:2018-07-19