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

Permission set 865 "D365 CUSTOMER, VIEW"

Base Application · System.Security.AccessControl

Open in Claude865.mdSource on GitHub

Across versions

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

Neighbourhood 1 connected objects and pages

Permission set extension 5908 "SERV D365 CUSTOMER VIEW" (extended by)SERV D365 CUSTOMER VIEW

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

Properties

Property Value
Caption Dynamics 365 View customers
Permissions tabledata “Contact Profile Answer” = R, tabledata “Cust. Invoice Disc.” = R, tabledata “Cust. Ledger Entry” = R, tabledata “Customer Bank Account” = R, tabledata “Item Reference” = R, tabledata “Profile Questionnaire Line” = R, tabledata “Reminder/Fin. Charge Entry” = R, tabledata “Shipping Agent Se…

Extended by

Countries that replace it

RU

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 1 sources