community postIntegration & APIscommunity - not Microsoftreviewed - checked by Opus

BC Friday Tips #41 Line Separator in Data Exchange Definition

A hidden Line Separator field in Data Exchange Definition allows importing files with different line break formats (LF or CR) without custom development. The field is not visible through normal personalization but can be accessed via Configuration Package or code modifications.

post That NAV Guy

Teddy Herryanto · 2025-08-01 · 95 words · about 1 min

"This field is hidden and cannot be enabled through Personalize."

Key points

  • Data Exchange Definition has a hidden Line Separator field for handling different line break types
  • Supports LF (Line Feed) and CR (Carriage Return) line breaks without requiring development
  • Field cannot be shown through the Personalize feature
  • Can be accessed through Configuration Package or AL development modifications

Quotes

  • “This field is hidden and cannot be enabled through Personalize.” (Alerts users that standard personalization methods won’t work to access this functionality.)
  • “This is useful when you need to import files that use LF (Line Feed) or CR (Carriage Return) line breaks.” (Explains the practical business value of the Line Separator feature for handling diverse file formats.)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

  • table “Data Exchange Definition”

Not found in BC28-30: table “Data Exchange Definition”.

Context

  • Features: Data Exchange Definition, Line Separator field, Configuration Package, File import, Line break handling

Source: That NAV Guy, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.