Page 9861 "AAD Application Card"
Base Application · System.Environment.Configuration
Across versions
- BC23-24present
- BC251 procedures changed
- BC26-28unchanged
- BC291 procedures added
- BC30unchanged
Neighbourhood 5 connected objects and pages
Base Application · System.Environment.Configuration · captioned “Microsoft Entra Application Card” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Microsoft Entra Application Card |
| SourceTable | AAD Application |
| PageType | Card |
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 |
|---|---|---|---|
| General | Client ID | Client Id | Specifies the client ID for the app. |
| Description | Description | Specifies a description of the app. The description will be automatically added in the User Name field of the card the first time the app is enabled. | |
| State | State | Specifies if the app is enabled or disabled. | |
| Contact Information | Contact Information | Specifies the contact information of the app. | |
| Extension | App ID | App ID | Specifies the app ID of the extension. |
| App Name | App Name | Specifies the app name of the extension. | |
| User information | User ID | User ID | Specifies the unique ID (GUID) assigned to the application. This field is automatically filled in once the app is enabled. The user ID. like the user name, is used to indicate sessions and operations that are run by the app. |
| User Name | Username |
Specifies the user name assigned to the app. This field is automatically filled in with the value of the Description field once the app is enabled. The user name, like the user ID, is used to indicate sessions and operations that are run by the app.. | |
| User Telemetry ID | TelemetryUserId |
Specifies a telemetry ID assigned to the app which can be used for troubleshooting purposes. | |
| General | ShowEnableWarning | ShowEnableWarning |
— |
| ShowInitializeUserWarningField | ShowInitializeUserWarning |
— | |
| Content | User Permission Sets | part Page 9801 “User Subform” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Grant Consent | Grant consent for this application to access data from Business Central. |
Procedures
4 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord
Relations
- source table Table 9012 “AAD Application”
Pages and codeunits on this table
- Page 9860 “AAD Application List” (card page)
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.
- Codeunit 5465 “Graph Mgt - General Tools” (2 calls:
GrantConsent → StripBrackets,OnAfterGetCurrRecord → StripBrackets) - Codeunit 501 “OAuth2” (1 call:
GrantConsent → RequestClientCredentialsAdminPermissions) - Codeunit 8821 “AAD Application Setup” (1 call:
OnAfterGetCurrRecord → GetD365BCForVEAppId)
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: "AAD Application Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.