When glide_list field is mandatory with Data Policy, "Add/Remove multiple" button doesn't work if another field on the form has been modified - Support and Troubleshooting

When glide_list field is mandatory with Data Policy, "Add/Remove multiple" button doesn't work if another field on the form has been modified Issue When a Glide LIST type field is made mandatory via a DATA POLICY and a form has unsaved changes, the "Add/Remove multiple" icon on the LIST field doesn't work. It shows empty/white screen in the dialog window.

Steps to reproduce this behavior:

Create a new LIST type field on any table (say Incident) Create a new Data Policy and make this LIST type field "Mandatory" Open any incident record which follows the data policy and has the LIST field as mandatory Change/Update any other field present in the form (say, Short description or Description) Now, click the LIST field created in step1, click on the "Add/Remove multiple" icon The dialog is empty and an error is observed in the browser console like below:

Uncaught TypeError: Cannot read property 'style' of null at changeStyles (eval at evalScript (js_includes_doctype.jsx?v=04-08-2021_0044&lp=Sat_Apr_10_06_05_08_PDT_2021&c=35_1305:84), :4:82) at HTMLIFrameElement.iFrame.onload (eval at evalScript (js_includes_doctype.jsx?v=04-08-2021_0044&lp=Sat_Apr_10_06_05_08_PDT_2021&c=35_1305:84), :12:4) Release All Releases

Cause This is expected behavior and working as per the design of Data Policies. Clicking the "add/remove multiple" button saves the current record, so if any field has been modified, the data policy will be enforced at that moment.

Resolution Go to the respective data policy which is making the LIST field mandatory Click on the related link "Convert this to UI Policy" to create a new UI policy. Deactivate the data policy.