BC Observatoryunofficial, made by waldo
permissionsetextensionAdministration & Setupofficial - Microsoftderived - from the source, no model text

Permission set extension 5919 "SERV D365PREM SMG SETUP"

Base Application · System.Security.AccessControl

Open in Claude5919.mdSource on GitHub

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28-30unchanged

Neighbourhood 1 connected objects and pages

Permission set 6524 "D365PREM SMG, SETUP" (relates to)D365PREM SMG, SETUP

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 · BC27-30 · source at ea08af5e · facts from BC29

Extends D365PREM SMG, SETUP.

Properties

Property Value
Permissions tabledata “Fault Area” = RIMD, tabledata “Fault Code” = RIMD, tabledata “Fault Reason Code” = RIMD, tabledata “Fault/Resol. Cod. Relationship” = RIMD, tabledata Loaner = RIMD, tabledata “Loaner Entry” = RIMD, tabledata “Repair Status” = RIMD, tabledata “Resolution Code” = RIMD, tabledata “Resource L…

Relations

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: "permissionsetextension", object_name: "SERV D365PREM SMG SETUP"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources