Page 1833 "Teams Centralized Deployment"
Base Application · System.Apps
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · System.Apps · captioned “Teams App Centralized Deployment” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Teams App Centralized Deployment |
| PageType | NavigatePage |
| UsageCategory | Administration |
| ApplicationArea | Basic, Suite |
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 |
|---|---|---|---|
| TopBannerStandardGrp | MediaResourcesStandard | MediaResourcesStandard."Media Reference" |
— |
| TopBannerDoneGrp | MediaResourcesDone | MediaResourcesDone."Media Reference" |
— |
| Set up the Business Central app for Teams | LearnMoreOptionsToDeploy | LearnMoreOptionsToDeployLbl |
— |
| Para2.1.2 | TeamAdminCenterSetup | TeamsAdminCenterLbl |
— |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Set up Microsoft 365 licenses | — | |
| Back | — | ||
| Next | — | ||
| Done | — | ||
| Continue with setup | — | ||
| Okay | — |
Procedures
LaunchFromM365Guide()(internal)
Plus 7 local procedures.
Triggers
OnInit, OnOpenPage
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 1990 “Guided Experience” (1 call:
CloseGuide → CompleteAssistedSetup) - Codeunit 4030 “Client Type Management” (1 call:
LoadTopBanners → GetCurrentClientType) - Codeunit 457 “Environment Information” (1 call:
OnInit → IsSaaS)
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: "Teams Centralized Deployment"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.