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

Table 6300 "Azure AD App Setup"

Base Application · System.Azure.Identity

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC253 procedures added, 1 fields changed
  4. BC261 fields changed
  5. BC27unchanged
  6. BC281 fields changed, 1 procedures removed
  7. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Page 6301 "Azure AD App Setup Part" (pages and codeunits on it)Azure AD App Setup PartCreate 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 “Microsoft Entra App Setup” · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 6301 “Azure AD App Setup Part” (1 Learn page).

Properties

Property Value
Caption Microsoft Entra App Setup
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 App ID Guid — NotBlank
2 Secret Key Δ BC25 Δ BC26 Δ BC28 BLOB — obsolete Removed 28.0; #if not CLEANSCHEMA28
3 Primary Key Integer — AutoIncrement
4 Redirect URL Text[150] —
5 Isolated Storage Secret Key Guid —

Keys

  • Key1: Primary Key (clustered)

Procedures

  • GetSecretKeyFromIsolatedStorageAsSecretText(): SecretText + BC25
  • SetSecretKeyToIsolatedStorage(SecretKey: SecretText) Δ BC25 + BC25 − BC28

Plus 1 local procedures.

Triggers

OnInsert

Pages and codeunits on this table

Deprecations

  • field Secret Key: Removed 28.0 (#if not CLEANSCHEMA28), “The Secret Key has been moved to Isolated Storage. Use GetSecretKeyFromIsolatedStorage/SetSecretKeyToIsolatedStorage to retrieve or set the Secret Key.”

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

Evidence 1 sources