Table 1223 "Data Exch. Column Def"
Base Application · System.IO
Across versions
- BC23present
- BC241 fields changed, 1 procedures removed
- BC25-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 1216 “Data Exch Col Def Part” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | Data Exch. Column 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] | — | TableRelation Table 1222 “Data Exch. Def” (Data Exch. Def); NotBlank |
| 2 | Column No. | Integer | Specifies the number that reflects the column’s position on the line in the file. via Page 1216 “Data Exch Col Def Part” | NotBlank |
| 3 | Name | Text[250] | Specifies the name of the column. via Page 1216 “Data Exch Col Def Part” | |
| 4 | Show | Boolean | Specifies that the element is shown in the data exchange definition. via Page 1216 “Data Exch Col Def Part” | |
| 5 | Data Type Δ BC24 | Option | Specifies if the data to be exchanged is of type Text, Date, or Decimal. via Page 1216 “Data Exch Col Def Part” | OptionCaption: Text,Date,Decimal,DateTime,Boolean |
| 6 | Data Format | Text[100] | Specifies the format of the data, if any. For example, MM-DD-YYYY if the data type is Date. via Page 1216 “Data Exch Col Def Part” | |
| 7 | Data Formatting Culture | Text[10] | Specifies the culture of the data format, if any. For example, en-US if the data type is Decimal to ensure that comma is used as the .000 separator, according to the US format. This field is only relevant for import. via Page 1216 “Data Exch Col Def Part” | |
| 8 | Description | Text[100] | Specifies a description of the column, for informational purposes. via Page 1216 “Data Exch Col Def Part” | |
| 10 | Data Exch. Line Def Code | Code[20] | — | TableRelation Table 1227 “Data Exch. Line Def” (“Data Exch. Line Def”.Code where(“Data Exch. Def Code” = field(“Data Exch. Def Code”))); NotBlank |
| 11 | Length | Integer | Specifies the length of the fixed-width line that holds the column if the file is of type Fixed Text. via Page 1216 “Data Exch Col Def Part” | |
| 12 | Constant | Text[30] | Specifies any data that you want to export in this column, such as extra information about the payment type. via Page 1216 “Data Exch Col Def Part” | |
| 13 | Path | Text[250] | Specifies the position of the element in the related XML schema. via Page 1216 “Data Exch Col Def Part” | |
| 14 | Negative-Sign Identifier | Text[30] | Specifies the value that is used in the data file to identify negative amounts, in data files that cannot contain negative signs. This identifier is then used to reverse the identified amounts to negative signs during import. via Page 1216 “Data Exch Col Def Part” | |
| 15 | Text Padding Required | Boolean | Specifies that the data must include text padding. via Page 1216 “Data Exch Col Def Part” | |
| 16 | Pad Character | Text[1] | Specifies that text padding. via Page 1216 “Data Exch Col Def Part” | |
| 17 | Justification | Option | Specifies if the column justification is left or right. via Page 1216 “Data Exch Col Def Part” | OptionCaption: Right,Left |
| 18 | Use Node Name as Value | Boolean | Specifies if the node name should be used as value for file types Xml or Json during import. via Page 1216 “Data Exch Col Def Part” | |
| 19 | Blank Zero | Boolean | Specifies if the element is epmty if equal to 0. via Page 1216 “Data Exch Col Def Part” | |
| 20 | Export If Not Blank | Boolean | Specifies if the value of this column must be exported only if it is not blank. via Page 1216 “Data Exch Col Def Part” |
Keys
- Key1: Data Exch. Def Code, Data Exch. Line Def Code, Column No. (clustered)
Procedures
InsertRec(DataExchDefCode: Code[20]; DataExchLineDefCode: Code[20]; ColumnNo: Integer; NewName: Text[250]; NewShow: Boolean; DataType: Option; DataTypeFormatting: Text[100]; DataFormattingCulture: Text[10]; NewDescription: Text[50])InsertRecForExport(DataExchDefCode: Code[20]; DataExchLineDefCode: Code[20]; ColumnNo: Integer; NewName: Text[250]; DataType: Option; DataFormat: Text[100]; NewLength: Integer; NewConstant: Text[30])InsertRecordForImport(DataExchDefCode: Code[20]; DataExchLineDefCode: Code[20]; ColumnNo: Integer; NewName: Text[250]; NewDescription: Text[100]; NewShow: Boolean; DataType: Option; DataFormat: Text[100]; DataFormattingCulture: Text[10])ValidateRec()IsDataFormatRequired(): BooleanIsDataFormattingCultureRequired(): BooleanSetXMLDataFormattingValues(SimpleDataType: Text)IsOfDataLine(): Boolean
Plus 2 local procedures.
Triggers
OnDelete, OnInsert, OnModify
Relations
- Data Exch. Def Code: TableRelation Table 1222 “Data Exch. Def”
- Data Exch. Line Def Code: TableRelation Table 1227 “Data Exch. Line Def”
Referenced by
1 fields in 1 objects relate to this table (TableRelation or CalcFormula).
- Table 1225 “Data Exch. Field Mapping”: Column No.
Pages and codeunits on this table
- Page 1216 “Data Exch Col Def Part” (source table)
Countries that replace it
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: "table", object_name: "Data Exch. Column Def"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.