Page 1200 "Bank Export/Import Setup"
Base Application · Microsoft.Bank.Setup
Across versions
- BC23-26present
- BC272 procedures added
- BC28-30unchanged
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Bank.Setup · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Bank Export/Import Setup |
| SourceTable | Bank Export/Import Setup |
| PageType | List |
| UsageCategory | Administration |
| 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 | Code | Code | Specifies a code for the Bank Export/Import setup. from the table field |
| Name | Name | Specifies the name of the bank export/import setup. from the table field | |
| Direction | Direction | Specifies if this setup will be used to import a bank file or to export a bank file. from the table field | |
| Processing Codeunit ID | Processing Codeunit ID | Specifies the codeunit that will import the bank statement data. from the table field | |
| Processing Codeunit Name | Processing Codeunit Name | Specifies the name of the codeunit that will import the bank statement data. from the table field | |
| Processing XMLport ID | Processing XMLport ID | Specifies the XMLport through which the bank statement data is imported. from the table field | |
| Processing XMLport Name | Processing XMLport Name | Specifies the name of the XMLport through which the bank statement data is imported. from the table field | |
| Data Exch. Def. Code | Data Exch. Def. Code | Specifies a code that represents the xml file with a data exchange definition that you have created in the Data Exchange Framework. from the table field | |
| Preserve Non-Latin Characters | Preserve Non-Latin Characters | Specifies that non-latin characters in the bank statement files are preserved during import. from the table field | |
| Check Export Codeunit | Check Export Codeunit | Specifies the codeunit that validates payment lines when you use the Export Payments to File action in the Payment Journal window. from the table field | |
| Check Export Codeunit Name | Check Export Codeunit Name | Specifies the name of the codeunit that validates payment lines when you use the Export Payments to File action in the Payment Journal window. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | SEPACAMT5300108 | Sets up a bank import format for SEPA CAMT 053.001.08 files |
Trigger event subscribers
- OnAfterGetCurrRecordEvent: Codeunit 20117 “AMC Bank Assisted Mgt.” ShowAssistedSetupNotificationBankExportImportSetup
Procedures
2 local procedures, no public ones.
Relations
- source table Table 1200 “Bank Export/Import Setup”
Pages and codeunits on this table
- Table 1200 “Bank Export/Import Setup” (drill-down page)
- Table 1200 “Bank Export/Import Setup” (lookup page)
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 104000 “Upgrade - BaseApp” (1 call:
UpgradeSEPACAMT05300108 → UpgradeSEPACAMT05300108)
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: "Bank Export/Import Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.