assigned_to not editable on form – no ACL/UI issue,

[MotapotulaN]

We are facing an issue where the Assigned To field is not editable on a custom task-like table in one instance, while the same configuration works fine in another instance.

Key observations:

• No field-level or table-level ACL is blocking write access.

• Dictionary entry and UI policies are identical in both instances.

• Client scripts and g_form.setReadOnly() have no effect.

• The field remains read-only even for admin users.

Has anyone encountered a case where server-side Business Rule recursion or repeated assignment logic causes the Assigned To field to become non-editable, even though no ACL/UI policy enforces read-only?

[Ankur Bawiskar]

@MotapotulaN 

is there any dictionary override which is making it readonly?

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

[yashkamde]

Hello @MotapotulaN ,

Check the Dictionary override record entry for your assigned to field, If not causing any issue from there..

Then create one write acl on that assigned_to field Level  -> give the role you want -> then check if the field is now read only or what...

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