Page 1061 "Select Payment Service"
Base Application · Microsoft.Bank.Setup
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Bank.Setup · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Select Payment Service |
| SourceTable | Payment Service Setup |
| PageType | StandardDialog |
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 |
|---|---|---|---|
| Control3 | Available | Available | Specifies that the icon and link to the payment service will be inserted on the outgoing sales document. from the table field |
| Name | Name | Specifies the name of the payment service. from the table field | |
| Description | Description | Specifies the description of the payment service. from the table field | |
| Content | SetupPaymentServices | SetupPaymentServicesLbl |
— |
Triggers
OnQueryClosePage
Relations
- source table Table 1060 “Payment Service Setup”
Called by
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.
- Table 1060 “Payment Service Setup” (1 call:
SelectPaymentService → (object))
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: "Select Payment Service"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.