User cannot write to custom table

[RichGK1]

I have created an application in studio where the table extends task.

I assign the role needed for a user to access the table but when impersonating the user the fields are greyed out on the table form. The user can access all other aspects of the application and modules that are controlled by the same role OK. Also the user can create records in the table when clicking submit.

The CRWD access controls that are automatically created are all table.none

Is this something to do with inheriting task?

[rajneeshbaranwa]

Does this user has ITIL role and you also need to check if this user is satisfying all edit ACL condition on TASK table as well.

Providing ITIL role to the user worked for me.

[RichGK1]

Yes I see what you mean. I added itil role and then the user could edit all fields.

However in this scenario I wanted a table inherited from task that the user could write to but not give them access to everything else that an itil user gets.

I thought that inheriting the table and setting a specific write table.* rule would overwrite the inherited rules?

[RichGK1 · Accepted solution]

OK I've done some reading and even though the rules for the custom table are table.none, the system will check for these and then check the parent task table to see if there are any rules applied there.

As there definitely are rules and they are more specific these are overriding the generic child table rules.

Long story short in order to inherit from the task table and allow users to fully utilise the child table you need to assign the task_editor role to that user as well as the new roles for the child table.