I am engineering custom security roles and running into UI behavior inconsistencies when applying security trimming to complex form elements in D365 F&O.
What is the correct architectural approach to handle security trimming for nested sub-menus, standard action pane tabs, and flyout drop dialogs? Specifically, if a user’s role explicitly denies access to the underlying Display or Action Menu Items within a flyout container, how do we ensure the parent container itself (e.g., the Action Pane tab or Menu Button) correctly trims out and disappears? Are we forced to manipulate the NeededPermission properties directly on the form controls, or should the framework seamlessly trim the parent if all child nodes are inaccessible?

Report
All responses (
Answers (