Fields in extended "Task" table became read-only w/o UI policy direction.

[C_dric Chen]

Greetings, everyone.

Long story short: I extended the "Task" table for my app. When I impersonate another user, some of the fields that came from the "Task" table became read-only, even though none of them are affected by any UI policies.

As illustrated above, none of these fields are affected by any UI policies. The only automation is a flow that automatically populates the "Due Date" field.

For unknown reason, these fields inside the red rectangle became read-only when I impersonate another user. This is strange, because I've defined the roles in such a way that all users who have access to this extended "Task" table should have read/write access to this table. (The "Project Lead" and "Additional Assignees" fields are rendered read-only by a UI policy.)

Does anyone have any ideas?

[Musab Rasheed]

Hello,

Please check ACL then, enable Security debugger and see which ACL is affecting, Mark my answer as correct if that helps.

Regards

[Aman Kumar S · Accepted solution]

Hey,

These fields are read only due to ACL on Task table, please override them by adding Write ACL of your own on your extended table and also field specific ACls

Feel free to mark correct, If I answered your query.

Will be helpful for future visitors looking for similar questions 🙂

[C_dric Chen]

Problem solved! Thank you, both of you.

[Aman Kumar S]

@Cédric Chen 

Glad that it worked out for you.

Feel free to mark correct, If I answered your query.

Will be helpful for future visitors looking for similar questions 🙂