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

Codeunit 8820 "AAD Application Interface"

Base Application · System.Environment.Configuration

Open in Claude8820.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 8821 "AAD Application Setup" (calls, 4 links)AAD Application Setup

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.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29

Procedures

  • CreateAADApplication(ClientId: Guid; ClientDescription: Text[50]; ContactInformation: Text[50])
  • CreateAADApplication(ClientId: Guid; ClientDescription: Text[50]; ContactInformation: Text[50]; EnableAADApplication: Boolean)
  • ModifyAADApplicationDescription(ClientId: Guid; ClientDescription: Text[50])

Triggers

OnRun

Called by

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

  • Codeunit 8821 “AAD Application Setup” (4 calls: CreateDynamics365BusinessCentralforVirtualEntitiesAAdApplication → CreateAADApplication, CreateExpenseAgentAADApplications → CreateAADApplication, CreatePowerPagesAAdApplications → CreateAADApplication, …)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "codeunit", object_name: "AAD Application Interface"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources