permissionsetAdministration & Setupofficial - Microsoftderived - from the source, no model text

Permission set 5117 "D365 AUTOMATION"

Base Application · System.Security.AccessControl

Across versions

  1. BC23-24present
  2. BC25declaration changed
  3. BC26-30unchanged

Neighbourhood 6 connected objects and pages

Permission set extension 20766 "D365 AUTOMATION - APIV2" (extended by)D365 AUTOMATION - APIV2Permission set extension 5503 "D365 AUTOMATION - APIV1" (extended by)D365 AUTOMATION - APIV1Permission set extension 5901 "SERV D365 AUTOMATION" (extended by)SERV D365 AUTOMATIONPermission set extension 6091 "D365 AUTOMATION - FATS" (extended by)D365 AUTOMATION - FATSPermission set extension 6610 "FS D365 AUTOMATION" (extended by)FS D365 AUTOMATIONPermission set extension 99000750 "MFG D365 AUTOMATION" (extended by)MFG D365 AUTOMATION

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · System.Security.AccessControl · captioned “Dynamics 365 Automation” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dynamics 365 Automation
Access Public
Permissions system “Tools, Security, Roles” = X, codeunit * = X, query * = X, report * = X, table * = X, xmlport * = X, tabledata “Add-in” = imd, tabledata “Aggregate Permission Set” = Rimd, tabledata “All Profile” = imd, tabledata “All Profile Extension” = imd, tabledata “All Profile Page Metadata” = imd, tabl…

Extended by

Recent changes

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 AUTOMATION"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources