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

Page 1215 "Data Exch Line Def Part"

Base Application · System.IO

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 1227 "Data Exch. Line Def" (relates to)Data Exch. Line DefDefine how data is exchanged electronically (Learn pages)Define how data is exchanged…

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 · captioned “Line Definitions” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Line Definitions
SourceTable Data Exch. Line 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 Line Type Line Type Specifies the type of the line in the file.
Code Code Specifies the line in the file.
Name Name Specifies the name of the mapping setup.
Column Count Column Count Specifies how many columns the line in the bank statement file has.
Data Line Tag Data Line Tag Specifies the position in the related XML schema of the element that represents the main entry of the data file.
Namespace Namespace 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.
Parent Code Parent Code 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.

Actions

Group Action ToolTip Runs
Processing Field Mapping Associates columns in the data file with fields in Dynamics 365. Page 1214 “Data Exch Mapping Card”

Triggers

OnAfterGetCurrRecord

Relations

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 Line Def Part"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources