Page 1229 "Payment File Error Details"
Base Application · Microsoft.Bank.Payment
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Bank.Payment · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Payment File Error Details |
| SourceTable | Payment Jnl. Export Error Text |
| PageType | CardPart |
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 |
|---|---|---|---|
| Content | Error Text | Error Text | Specifies the error that is shown in the Payment Journal window in case payment lines cannot be exported. from the table field |
| Additional Information | Additional Information | Specifies more information that may help you resolve the error. from the table field | |
| Support URL | Support URL | Specifies a web page containing information that may help you resolve the error. from the table field |
Relations
- source table Table 1228 “Payment Jnl. Export Error Text”
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: "Payment File Error Details"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.