Hi @PeteM1 ,
There is slight confusion in your below statements.
One that allows for creating but not editing of records for two roles (teammembers and requesters) ---> It meas both roles are able to create but not edit.
However, when I add an additional ACL write rule (shown below) selecting * in the fields field, it no longer allows the requesters to create records. ---> In the above statement you've mentioned both roles are able to create records. Do you mean create records or edit records in this statment as highilghted? In my understanding you are saying edit records instead of create records. I'm I correct?
If my understanding is correct, then what ever you've configured is working fine because the edit access you've given only to the team members role not the requester role.
If my understanding is wrong, then what ever you've configured is working fine here as well in this case because without giving edit access to the columns how could a role create the records?
You need to write something like this to work this out in your 2nd ACL. Change the below script according to your business logic.
if((gs.hasRole("teamMember") || gs.hasRole("Requestor")) && current.isNewRecord()){
answer = true;
}
else if(gs.hasRole("requestor") && !current.isNewRecord){
answer = true;
}
else
{
answer = false;
}
Please hit like button if my suggestion has helped you in any way.
Please mark correct if my response has solved your query.
Cheers,
Mohammed Basheer Ahmed.
