Page 1279 "Service Connections"
Base Application · Microsoft.Utilities
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Utilities · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Service Connections |
| SourceTable | Service Connection |
| PageType | List |
| UsageCategory | Lists |
| 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 |
|---|---|---|---|
| Group | Name | Name | Specifies the service. The description is based on the name of the setup page that opens when you choose the Setup. from the table field |
| Host Name | Host Name | Specifies the name of the web service. This is typically a URL. from the table field | |
| Status | Status | Specifies if the service is enabled or disabled. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Navigation | Setup | Get a connection to a service up and running or manage an connection that is already working. |
Procedures
4 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnInit, OnOpenPage
Relations
- source table Table 1400 “Service Connection”
Extended by
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” (2 calls:
CallSetup → AssistedSetupExistsAndIsNotComplete,CallSetup → Run) - Codeunit 5330 “CRM Integration Management” (1 call:
OnInit → RegisterAssistedSetup) - Codeunit 7200 “CDS Integration Mgt.” (1 call:
OnInit → RegisterAssistedSetup)
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: "Service Connections"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.