tableAL Developmentofficial - Microsoftderived - from the source, no model text

Table 1221 "Data Exch. Field"

Base Application · System.IO

Across versions

  1. BC23present
  2. BC241 fields changed
  3. BC25-30unchanged

Neighbourhood 4 connected objects and pages

Table 1220 "Data Exch." (relates to, 2 links)Data Exch.Table 1227 "Data Exch. Line Def" (relates to)Data Exch. Line DefPage 1221 "Bank Statement Line Details" (pages and codeunits on it)Bank Statement Line DetailsCodeunit 10 "Type Helper" (calls, 2 links)Type Helper

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
Caption Data Exch. Field
DataClassification CustomerContent
Permissions TableData “Data Exch. Field” = rimd

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. No. Integer — TableRelation Table 1220 “Data Exch.” (Data Exch.); NotBlank
2 Line No. Integer — NotBlank
3 Column No. Integer — NotBlank
4 Value Text[250] Specifies the value in a column in the imported bank statement file, such as account number, posting date, and amount. via Page 1221 “Bank Statement Line Details”
5 Node ID Text[250] —
6 Data Exch. Line Def Code Code[20] — TableRelation Table 1227 “Data Exch. Line Def” (“Data Exch. Line Def”.Code)
10 Parent Node ID Text[250] —
11 Data Exch. Def Code Δ BC24 Code[20] — FlowField: lookup(“Data Exch.”.“Data Exch. Def Code” where(“Entry No.” = field(“Data Exch. No.”)))
16 Value BLOB BLOB —

Keys

  • Key1: Data Exch. No., Line No., Column No., Node ID (clustered)

Events published

  • OnInsertRecXMLFieldWithParentNodeIDOnBeforeInsert(var DataExchField: Record "Data Exch. Field"; var NodeValue: Text) (integration)

Procedures

  • InsertRec(DataExchNo: Integer; LineNo: Integer; ColumnNo: Integer; NewValue: Text; DataExchLineDefCode: Code[20])
  • InsertRecXMLField(DataExchNo: Integer; LineNo: Integer; ColumnNo: Integer; NodeId: Text[250]; NodeValue: Text; DataExchLineDefCode: Code[20])
  • InsertRecXMLFieldWithParentNodeID(DataExchNo: Integer; LineNo: Integer; ColumnNo: Integer; NodeId: Text[250]; ParentNodeId: Text[250]; NodeValue: Text; DataExchLineDefCode: Code[20])
  • InsertRecXMLFieldDefinition(DataExchNo: Integer; LineNo: Integer; NodeId: Text[250]; ParentNodeId: Text[250]; NewValue: Text[250]; DataExchLineDefCode: Code[20])
  • GetFieldName(): Text
  • DeleteRelatedRecords(DataExchNo: Integer; LineNo: Integer)
  • GetValue(): Text
  • SetValue(NewValue: Text)
  • SetValueWithoutModifying(NewValue: Text)

Relations

Pages and codeunits on this table

Calls

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.

Countries that replace it

RU

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

Evidence 1 sources