45
Since the Microsoft updates on Tuesday night we have not been able to use transaction import. All control files we have been using for years. Now we get message system 8201 invalid level specified treat as a comment. no errors detected but will not import. Anyone experiencing this?
Check to see if this is a BOM problem.
On every Windows system, text files such as transaction import data files can come in two main flavors: ANSI and Unicode. Modern Windows systems (the Windows NT branch) have a native Unicode approach, and older ones (the Windows 95 branch) have native ANSI setup. Unicode allows for more multilengual characters.
An Unicode text file can also have an invisible preamble, which is called the BOM (Byte Order Mark). An Unicode sensible application will read the file with no problem.
The Dynamics SL application is traditionally built strictly as an ANSI program. If you feed in a BOM-Unicode data file to the Transation Import, the first line will read [BOM]Batch instead of Batch and a 8021 error triggers.
To check if this is the case, open any data file with a text editor (Notepad will do) and then do a "Save As..." and make sure the encoding is set as ANSI (not Unicode, not UTF-8, not UTF-16). Then try again the import and see if it works. This would mean that the latest updates caused that now an Unicode enforcement is applied somewhere in the pipeline of your data files.
For what it is worth,
I have had sporadic instances in the past where the import will not accept Level0, Level1, etc but accepts Batch, Invoice, etc as the levels in the data file.
#1
André Arnaud de Cal...
291,791
Super User 2024 Season 2
#2
Martin Dráb
230,488
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
