Page 1210 "Data Exch Def Card"

Base Application · System.IO · captioned “Data Exchange Definition” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Data Exchange Definition
SourceTable	Data Exch. Def
PageType	Card

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
Control19	Code	Code	Specifies a code that identifies the data exchange setup.
	Name	Name	Specifies the name of the data exchange definition.
	File Type	File Type	Specifies what type of file the data exchange definition is used for. You can select between three file types.
	Type	Type	Specifies what type of exchange the data exchange definition is used for.
	Data Handling Codeunit	Data Handling Codeunit	Specifies the codeunit that transfers data in and out of tables in Microsoft Dynamics 365.
	Validation Codeunit	Validation Codeunit	Specifies the codeunit that is used to validate data against pre-defined business rules.
	Reading/Writing Codeunit	Reading/Writing Codeunit	Specifies the codeunit that processes imported data prior to mapping and exported data after mapping.
	Reading/Writing XMLport	Reading/Writing XMLport	Specifies the XMLport through which an imported data file or service enters prior to mapping and through which exported data exits when it is written to a data file or service after mapping.
	Ext. Data Handling Codeunit	Ext. Data Handling Codeunit	Specifies the codeunit that transfers external data in and out of the Data Exchange Framework.
	User Feedback Codeunit	User Feedback Codeunit	Specifies the codeunit that does various clean-up after mapping, such as marks the lines as exported and deletes temporary records.
File Type: Variable/Fixed	File Encoding	File Encoding	Specifies the encoding of the file to be imported. This field is only relevant for import.
	Column Separator	Column Separator	Specifies how columns in the file are separated if the file is of type Variable Text.
	Custom Column Separator	Custom Column Separator	Specifies how columns in the file are separated if the file is of a custom type.
	Line Separator	Line Separator	Specifies how lines in the file are separated if the file is of type Variable Text.
Type: Import	Header Lines	Header Lines	Specifies how many header lines exist in the file. This ensures that the header data is not imported. This field is only relevant for import.
	Header Tag	Header Tag	Specifies the text of the first column on the header line.
	Footer Tag	Footer Tag	Specifies the text of the first column on the footer line. If a footer line exists in several places in the file, enter the text of the first column on the footer line to ensure that the footer data is not imported. This field is only relevant for import.
Content	Line Definitions	part Page 1215 “Data Exch Line Def Part”	—
	Column Definitions	part Page 1216 “Data Exch Col Def Part”	—

Actions

Group	Action	ToolTip	Runs
Processing	Import Data Exchange Definition	Import a data exchange definition from a bank file that is located on your computer or network. The file type must match the value of the File Type field.
	Export Data Exchange Definition	Export the data exchange definition to a file on your computer or network. You can then upload the file to your electronic bank to process the related transfers.

Triggers

OnInsertRecord, OnOpenPage

Relations

source table Table 1222 “Data Exch. Def”

Pages and codeunits on this table

Page 1211 “Data Exch Def List” (card page)

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.

Codeunit 9610 “XSD Parser” (1 call: CreateDataExchDefForCAMT → (object))

Documented on Microsoft Learn

Define how data is exchanged electronically

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: "Data Exch Def Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.