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

Permission set extension 5913 "SERV D365 TEAM MEMBER"

Base Application · System.Security.AccessControl

Open in Claude5913.mdSource on GitHub

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28declaration changed
  4. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Permission set 7931 "D365 TEAM MEMBER" (relates to)D365 TEAM MEMBER

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 D365 TEAM MEMBER.

Properties

Property Value
Permissions tabledata “Service Header” = Rm, tabledata “Service Invoice Header” = Rm, tabledata “Service Shipment Header” = Rm, tabledata “Service Cr.Memo Header” = Rm, tabledata “Contract Change Log” = RM, tabledata “Contract Gain/Loss Entry” = RM, tabledata “Contract Group” = RM, tabledata “Contract Trend Buf…

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

Evidence 1 sources