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

Permission set 618 "D365 DYN CRM READ"

Base Application · System.Security.AccessControl

Open in Claude618.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25declaration changed
  4. BC26-30unchanged

Neighbourhood 1 connected objects and pages

Permission set extension 6612 "FS D365 DYN CRM READ" (extended by)FS D365 DYN CRM READ

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 Sales Integration - Read” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dynamics 365 Sales Integration - Read
Permissions tabledata “CDS Available Virtual Table” = R, tabledata “CDS BC Table Relation” = R, tabledata “CDS Company” = R, tabledata “CDS Connection Setup” = R, tabledata “CDS Coupled Business Unit” = R, tabledata “CDS Environment” = R, tabledata “CDS Solution” = R, tabledata “CDS Teammembership” = R, tableda…

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

Evidence 1 sources