Page 1216 "Data Exch Col Def Part"
Base Application · System.IO
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · System.IO · captioned “Column Definitions” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Column Definitions |
| SourceTable | Data Exch. Column Def |
| PageType | ListPart |
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 | Column No. | Column No. | Specifies the number that reflects the column’s position on the line in the file. |
| Name | Name | Specifies the name of the column. | |
| Data Type | Data Type | Specifies if the data to be exchanged is of type Text, Date, or Decimal. | |
| Data Format | Data Format | Specifies the format of the data, if any. For example, MM-DD-YYYY if the data type is Date. | |
| Data Formatting Culture | Data Formatting Culture | 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. | |
| Length | Length | Specifies the length of the fixed-width line that holds the column if the file is of type Fixed Text. | |
| Description | Description | Specifies a description of the column, for informational purposes. | |
| Path | Path | Specifies the position of the element in the related XML schema. | |
| Negative-Sign Identifier | Negative-Sign Identifier | 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. | |
| Constant | Constant | Specifies any data that you want to export in this column, such as extra information about the payment type. | |
| Show | Show | Specifies that the element is shown in the data exchange definition. | |
| Text Padding Required | Text Padding Required | Specifies that the data must include text padding. | |
| Pad Character | Pad Character | Specifies that text padding. | |
| Justification | Justification | Specifies if the column justification is left or right. | |
| Use Node Name as Value | Use Node Name as Value | Specifies if the node name should be used as value for file types Xml or Json during import. | |
| Blank Zero | Blank Zero | Specifies if the element is epmty if equal to 0. | |
| Export If Not Blank | Export If Not Blank | Specifies if the value of this column must be exported only if it is not blank. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Get File Structure | Prefill the lines of the column definitions according to the structure of a data file on your computer or network. |
Procedures
1 local procedures, no public ones.
Relations
- source table Table 1223 “Data Exch. Column Def”
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). 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 Col Def Part"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.