XMLPort doesn't recognize carriage return characters

JGV
Member Posts: 2
Hi, developers:
I'm working in a XMLPort in BC version 20. This XMLPort has next properties:
Direction = Import;
TextEncoding = UTF8;
Format = VariableText;
FieldDelimiter = '<none>';
FieldSeparator = '<TAB>';
UseRequestPage = false;
At the end of each line of .txt file there are LR and CR characters. However, when object is executed, all file is read in one line beacause carriage return characters aren't recognized.
Please, do you know if there are something wrong about XMLport in BC version 20? I worked in a similar XMLPort before in version 16 and it's working correctly.
Thank you
I'm working in a XMLPort in BC version 20. This XMLPort has next properties:
Direction = Import;
TextEncoding = UTF8;
Format = VariableText;
FieldDelimiter = '<none>';
FieldSeparator = '<TAB>';
UseRequestPage = false;
At the end of each line of .txt file there are LR and CR characters. However, when object is executed, all file is read in one line beacause carriage return characters aren't recognized.
Please, do you know if there are something wrong about XMLport in BC version 20? I worked in a similar XMLPort before in version 16 and it's working correctly.
Thank you
0
Best Answer
-
I beieve FieldDelimiter should be '<None>', not '<none>'
The property that is really important here isRecordSeparator
.
Please make sure it is '<NewLine>'. If it is not set, it should default to that value. You may, however try to set it explicitely.
I do not have access to a BC version 20 System right now, so I can't crosscheck.
Please also make sure your import file has proper NewLine sequeces, ie, 0x0d, 0x0a (<CR>,<LF>) sequences. (not inverted). Also make sure there is not a mix of Unix, Mac, and Windows EndOfLine sequences.
And finally make sure the file is valid UTF8.0
Answers
-
I beieve FieldDelimiter should be '<None>', not '<none>'
The property that is really important here isRecordSeparator
.
Please make sure it is '<NewLine>'. If it is not set, it should default to that value. You may, however try to set it explicitely.
I do not have access to a BC version 20 System right now, so I can't crosscheck.
Please also make sure your import file has proper NewLine sequeces, ie, 0x0d, 0x0a (<CR>,<LF>) sequences. (not inverted). Also make sure there is not a mix of Unix, Mac, and Windows EndOfLine sequences.
And finally make sure the file is valid UTF8.0 -
Hi, vaprog:
You are right, it was about FieldDelimiter property as you said.
Thank you0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions