Table 1227 "Data Exch. Line Def"

Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 1215 “Data Exch Line Def Part” (1 Learn page), Page 1227 “Pmt. Export Line Definitions” (1).

Properties

Property	Value
Caption	Data Exch. Line Def
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Data Exch. Def Code	Code[20]	Specifies a code that identifies the data exchange definition. via Page 1212 “Data Exch Line Def Card”	TableRelation Table 1222 “Data Exch. Def” (“Data Exch. Def”.Code); NotBlank
2	Code	Code[20]	Specifies the line in the file. via Page 1212 “Data Exch Line Def Card”	NotBlank
3	Name	Text[100]	Specifies the name of the mapping setup. via Page 1212 “Data Exch Line Def Card”
4	Column Count	Integer	Specifies how many columns the line in the bank statement file has. via Page 1212 “Data Exch Line Def Card”
5	Data Line Tag	Text[250]	Specifies the position in the related XML schema of the element that represents the main entry of the data file. via Page 1215 “Data Exch Line Def Part”
6	Namespace	Text[250]	Specifies the namespace (uniform resource name (urn)) for a target document that is expected in the file for validation. You can leave the field blank if you do not want to enable namespace validation. via Page 1212 “Data Exch Line Def Card”
10	Parent Code	Code[20]	Specifies the parent of the child that is specified in the Code field in cases where the data exchange setup is for files with parent and children entries, such as a document header and lines. via Page 1215 “Data Exch Line Def Part”	TableRelation Table 1227 “Data Exch. Line Def” (“Data Exch. Line Def”.Code where(“Data Exch. Def Code” = field(“Data Exch. Def Code”)))
11	Line Type	Option	Specifies the type of the line in the file. via Page 1215 “Data Exch Line Def Part”	OptionCaption: Detail,Header,Footer

Keys

Key1: Data Exch. Def Code, Code (clustered)
Key2: Data Exch. Def Code, Parent Code
Key3: Data Line Tag

Procedures

InsertRec(DataExchDefCode: Code[20]; NewCode: Code[20]; NewName: Text[100]; ColumnCount: Integer)
ValidateNamespace(XMLNode: DotNet XmlNode)
GetPath(TableId: Integer; FieldId: Integer): Text

Triggers

OnDelete

Relations

Data Exch. Def Code: TableRelation Table 1222 “Data Exch. Def”
Parent Code: TableRelation Table 1227 “Data Exch. Line Def”

Referenced by

7 fields in 7 objects relate to this table (TableRelation or CalcFormula).

Table 1220 “Data Exch.”: Data Exch. Line Def Code
Table 1221 “Data Exch. Field”: Data Exch. Line Def Code
Table 1223 “Data Exch. Column Def”: Data Exch. Line Def Code
Table 1224 “Data Exch. Mapping”: Data Exch. Line Def Code
Table 1225 “Data Exch. Field Mapping”: Data Exch. Line Def Code
Table 1227 “Data Exch. Line Def”: Parent Code
Table 1238 “Data Exch. Field Grouping”: Data Exch. Line Def Code

Pages and codeunits on this table

Page 1212 “Data Exch Line Def Card” (source table)
Page 1215 “Data Exch Line Def Part” (source table)
Page 1227 “Pmt. Export Line Definitions” (source table)

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