From 63cde80c65a10e1224ed0d43179d7e515bbb3d9b Mon Sep 17 00:00:00 2001 From: Dennis Roczek Date: Fri, 23 Apr 2021 15:00:24 +0200 Subject: [PATCH] #2209 Updating Field Delimiter Field Delimiter Escaping is sadly not respected and produces problems. --- dynamics-nav/FieldDelimiter-Property.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/dynamics-nav/FieldDelimiter-Property.md b/dynamics-nav/FieldDelimiter-Property.md index 30c5c68ab..7f80ec79b 100644 --- a/dynamics-nav/FieldDelimiter-Property.md +++ b/dynamics-nav/FieldDelimiter-Property.md @@ -32,7 +32,9 @@ Specifies the text delimiter for a field. ## Remarks The default value is " (double straight quotes). -You can set the field delimiter in C/AL code so that the XMLport can import and export records with different delimiters. For example, if your XMLport must import from a file or stream where one record uses commas and another uses an empty string, you can change the field delimiter property at run time. +You can set the field delimiter in C/AL code so that the XMLport can import and export records with different delimiters. For example, if your XMLport must import from a file or stream where one record uses commas and another uses an empty string, you can change the field delimiter property at run time. + +Escaping the field delimiter within the field value as documented in [RFC 4180 standard](https://www.ietf.org/rfc/rfc4180.txt) is not respected. ## See Also [Properties](Properties.md)