Page 30133 "Shpfy Transaction Gateways"
Shopify · Microsoft.Integration.Shopify
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
Shopify · Microsoft.Integration.Shopify · captioned “Shopify Transaction Gateways” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Shopify Transaction Gateways |
| SourceTable | Shpfy Transaction Gateway |
| PageType | List |
| UsageCategory | None |
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 |
|---|---|---|---|
| General | Name | Name | Specifies the name of the gateway the transaction was issued through. |
Relations
- source table Table 30135 “Shpfy Transaction Gateway”
Pages and codeunits on this table
- Table 30135 “Shpfy Transaction Gateway” (drill-down page)
- Table 30135 “Shpfy Transaction Gateway” (lookup page)
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). 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: "Shpfy Transaction Gateways"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.