BC Observatoryunofficial, made by waldo
pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 9065 "Plan Configurations Part"

System Application · System.Azure.Identity

Open in Claude9065.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 9017 "Plan Configuration" (relates to)Plan ConfigurationPage 9069 "Plan Configuration Card" (pages and codeunits on it)Plan Configuration Card

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.

System Application · System.Azure.Identity · captioned “License Configurations” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption License Configurations
Extensible false
SourceTable Plan Configuration
PageType ListPart
Permissions tabledata “Plan Configuration” = r

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
Group Licenses Plan Name Specifies the name of the license.
Permissions Customized Customized Specifies if the permissions are customized.

Relations

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

Evidence 1 sources