Decorating an event subscriber with InherentPermissions 'R' is insufficient because users still need Insert permission to post sales orders
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. A company creates a Business Central app and a table named MyTable to store records when sales orders are posted. Users report the following issues: • The users receive permission errors related to MyTable. • Users are no longer able to post sales orders since installing the new app. • The users cannot access the list page created in MyTable. You need to resolve the user issues without creating new permission sets. You must use the principle of least privilege. Solution: Decorate the event subscriber used for inserting data in MyTable by entering (InherentPermissions(PermissionObjectType::TableData. Database::MyTable. 'R')] Does the solution meet the goal?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
InherentPermissions must grant every permission the task needs. Here the insert path is the missing piece, so a Read-only grant fails the goal even though it partially addresses permission errors and list access.
This question reuses the same scenario but applies InherentPermissions only at the event subscriber level with the value 'R' (Read). Because the reported issue includes the inability to post sales orders, which requires Insert, granting only Read leaves the core problem unresolved.
Do not be misled by the fact that Read helps with some errors; the question asks whether the solution meets the goal, and the missing Insert means it does not. Always map each reported issue to a required permission letter.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.