In one of our last projects we used an editable grid from Microsoft, but had a strange issue.
Read here how we detected and identified a missing privilege for editable grids.
During testing with an user account we found that the editable grid for a custom entity does not render. For admins is all fine.
This is how it should look.
This what it actually was.
First thing we’ve checked was whether someone has changed the form rendering mode because editable subgrids don’t work on legacy forms. But it was still correct set.
Also we checked the known editable grids limitations for fields from related entities, the state field, partylists, customer and composite fields. But there was no such field in the view.
Further we’ve checked the users security roles. They have a custom role, but it includes all privileges for the parent and child entity.
Next we proved what happens when we remove the editable grid control and use the read only version instead. As a result, everything was ok in the read only grid.
Now I had a look at the browser console and found an error . . . a few times.
As desperation act we gave the user the default sales person security role and were surprised that now everything worked fine.
Identify the missing privilege for editable grids
We compared the two security roles and identified the “prvReadRole” as origin of the issue.
It was set to “None Selected”. I assume it is needed by the editable grid control the check if the user has all necessary privileges to edit the records in his security roles.