pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 6301 "Azure AD App Setup Part"

Base Application · System.Azure.Identity

Across versions

  1. BC23-24present
  2. BC252 procedures added, 1 procedures changed
  3. BC26-27unchanged
  4. BC281 procedures removed
  5. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Table 6300 "Azure AD App Setup" (relates to)Azure AD App SetupCodeunit 6300 "Azure AD Mgt." (calls, 2 links)Azure AD Mgt.Create users according to licenses (Learn pages)Create users according to li…

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.Azure.Identity · captioned “” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption
SourceTable Azure AD App Setup
PageType CardPart

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Content Home page URL HomePageUrl Specifies the home page URL to enter when registering a Microsoft Entra application.
Reply URL RedirectUrl Specifies the reply URL to enter when registering a Microsoft Entra application.
Application ID AppId Specifies the ID that is assigned to the application when it is registered in Microsoft Entra ID. The ID is used for authenticating with Microsoft Entra ID. This is also referred to as the client ID.
Key SecretKey Specifies the secret key (or client secret) that is used along with the Application ID for authenticating with Microsoft Entra ID.

Procedures

  • Save()
  • ValidateFields()
  • SetReplyURLWithDefault()
  • SetAppDetails(ApplicationId: Guid; Key: SecretText) Δ BC25 + BC25 − BC28
  • GetRedirectUrl(): Text

Plus 1 local procedures.

Triggers

OnOpenPage

Relations

Calls

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.

Documented on Microsoft Learn

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). 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: "page", object_name: "Azure AD App Setup Part"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources