Permission set 191 "D365 SETUP"
Base Application · System.Security.AccessControl
Across versions
- BC23-27present
- BC28declaration changed
- BC29-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · System.Security.AccessControl · captioned “Dyn. 365 Company data setup” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Dyn. 365 Company data setup |
| Access | Public |
| Permissions | tabledata “Data Sensitivity” = RIMD, tabledata “NAV App Installed App” = Rimd, tabledata “Object Options” = IMD, tabledata “ABC Analysis Setup” = RIMD, tabledata “Acc. Sched. Cell Value” = D, tabledata “Acc. Sched. KPI Web Srv. Line” = RIMD, tabledata “Acc. Sched. KPI Web Srv. Setup” = RIMD, tableda… |
Extended by
- Permission set extension 5911 “SERV D365 SETUP”
- Permission set extension 8051 “Sub. Billing D365 Setup”
- Permission set extension 8862 “D365 SETUP - SBSI”
- Permission set extension 99000758 “MFG D365 SETUP”
Recent changes
- 2026-07-25 #9455 Update permissions for G/L Transaction table (main, BC30, fix)
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "permissionset", object_name: "D365 SETUP"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.