Page 6136 "E-Doc. Service Data Exch. Sub"
EDocument · Microsoft.eServices.EDocument.IO.Peppol
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.eServices.EDocument.IO.Peppol · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | E-Doc. Service Data Exch. Def. |
| PageType | ListPart |
| ApplicationArea | All |
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 |
|---|---|---|---|
| GroupName | Document Type | Document Type | Specifies the document type that will use data exchange for importing/exporting the data. |
| Impt. Data Exchange Def. Code | Impt. Data Exchange Def. Code | Specifies the data exchange code that is used for importing the data. | |
| Impt. Data Exchange Def. Name | Impt. Data Exchange Def. Name | Specifies the data exchange name that is used for importing the data. | |
| Expt. Data Exchange Def. Code | Expt. Data Exchange Def. Code | Specifies the data exchange code that is used for exporting the data. | |
| Expt. Data Exchange Def. Name | Expt. Data Exchange Def. Name | Specifies the data exchange name that is used for exporting the data. |
Relations
- source table Table 6139 “E-Doc. Service Data Exch. Def.”
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: "E-Doc. Service Data Exch. Sub"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.