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

Permission set 5759 "D365 BANKING"

Base Application · System.Security.AccessControl

Open in Claude5759.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Permission set extension 20108 "D365 BANKING - AMC" (extended by)D365 BANKING - AMCPermission set extension 8860 "D365 BANKING - SBSI" (extended by)D365 BANKING - SBSI

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

Properties

Property Value
Caption Dynamics 365 Banking
Permissions tabledata “Alloc. Account Distribution” = RIMD, tabledata “Allocation Account” = RIMD, tabledata “Allocation Line” = RIMD, tabledata “Analysis View” = rimd, tabledata “Analysis View Entry” = rim, tabledata “Analysis View Filter” = r, tabledata “Applied Payment Entry” = RIMD, tabledata “Bank Acc. Rec…

Extended by

Recent changes

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

Evidence 1 sources