Anyone else having trouble with forms not working with child table permissions?

[arpost]

Greetings, community. I am experiencing an issue that I think might be a bug but want to see if anyone can spot an issue on my end before I report it. I have a form that gives a permissions error every time a user tries to save it:

The form is saving to a table named RoleOffice and is a mapping between two other tables (Role and Office). The table permissions are set up as follows for users in a role I created named Admin; note that Read/Update/Create/Delete is enabled on RoleOffice:

The user has been assigned to the Admin web role, so by my read, this should all be working. One odd thing I noticed in the Design Studio when I selected permissions for the form is that Power Pages doesn't list the permission I have set up. It will show "top-level" permissions, but the RoleOffice child permission doesn't show:

Anyone have any ideas?

[Fubar · Accepted solution]

The error message you are seeing is usually correct, and can sometimes mean that there is a missing privilege for a Table that one of the Lookup fields is for or the main record if not enough to start with e.g. (only create but it also needs more privilleges).

First, if not already done so assign the Table permissions to a Web Role that is being used (e.g. just because you are admin you only get those Permissions that are assigned to a Web Role you are using or are Inheiting off [such as the out of the box Authenticated User web role]).

Sometimes it isn't needed, but technically as you have Lookup fields being used they would usually require append to and append privileges (one on the main record, the other on Lookup Table privilege), when a Lookup is populated in Dataverse for what the privileges mean see the 2nd table at this link  https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges#table-privileges

The quickest way to work out if it is the privileges you currently have is to open the Web Roles using the Portal/Power Pages Management App and turn on all the privileges and then clear the portal cache (either preview/sync or on the <sitedomain>/_services/about when logged in as a user with the Administrators Web Role assigned ) and see if you can then save (and if you can then tweak the Table Permissions so you end up with the minimum needed).

[arpost]

Thanks for the reply, @Fubar. Turns out it was the append settings. Needed to enable Append on the Role and Office tables and Append To on the RoleOffice table.