Page 6712 "Tenant Web Services Lookup"
Base Application · System.Integration
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · System.Integration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Tenant Web Services Lookup |
| SourceTable | Tenant Web Service |
| PageType | List |
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 | Object Type | Rec."Object Type" |
Specifies the Object Type of the data set. |
| Object ID | Rec."Object ID" |
Specifies the object ID for the data set. | |
| Service Name | Rec."Service Name" |
Specifies the data set name. |
Triggers
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 9750 “Web Service Management” (1 call:
OnOpenPage → LoadRecordsFromTenantWebServiceColumns)
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: "Tenant Web Services Lookup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.