assigned to field not becoming mandatory

[suresh kaliappa]

Hi all,

I created 1 custom client script to make assigned to field mandatory in dev instance. In dev instance it is working fine but i migrated the same code to QA without any changes. But same code not working in QA instance. The assigned to field not becoming mandatory.   so can someone please suggest what might be the issue?

[Ankur Bawiskar · Accepted solution]

@suresh kaliappa 

any other UI policy is making it non-mandatory in QA?

what debugging did you do?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[yashkamde]

Hello @suresh kaliappa ,

were there any issue in Update set while Preview?

Also try manually recreate the same script directly in QA, if it works perfectly. Same code, same settings !

If my response helped mark as helpful and accept the solution.

[Tanushree Maiti]

Hi @suresh kaliappa 

Check if  your QA instance has any existing Data Policy /UI Policy running on the assigned_to field.

If yes, it can override your Client Script as you know UI Policies usually run after Client Scripts.

[Aditya_hublikar]

Hello @suresh kaliappa ,

Have you checked whether your code changes were captured in the update set and migrated properly to QA? Also, check whether any other UI Policies or Client Scripts are applied to the same field and are making the Assigned to field non-mandatory. There might be conflicting configurations in the QA instance.

If this helps you then mark it as helpful and accept as solution.

Regards,

Aditya