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

Permission set 9921 "D365 VENDOR, EDIT"

Base Application · System.Security.AccessControl

Open in Claude9921.mdSource on GitHub

Across versions

  1. BC23-24present
  2. BC25declaration changed
  3. BC26unchanged
  4. BC27declaration changed
  5. BC28-30unchanged

Neighbourhood 2 connected objects and pages

Permission set extension 5914 "SERV D365 VENDOR, EDIT" (extended by)SERV D365 VENDOR, EDITPermission set extension 99000760 "MFG D365 VENDOR, EDIT" (extended by)MFG D365 VENDOR, EDIT

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 Create vendors” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dynamics 365 Create vendors
Permissions tabledata “Bank Account Ledger Entry” = rm, tabledata “Check Ledger Entry” = r, tabledata “Cont. Duplicate Search String” = RIMD, tabledata Contact = RIM, tabledata “Contact Business Relation” = RImD, tabledata “Contact Duplicate” = Rd, tabledata “Company Size” = rimd, tabledata Currency = RM, table…

Extended by

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

Evidence 1 sources