It's reasonably intuitive for a non-technical user to use (since it has pretty much the same control scheme as the familiar Notepad), but has enough technical t

It's reasonably intuitive for a non-technical user to use (since it has pretty much the same control scheme as the familiar Notepad), but has enough technical tools built into it that you can do some serious diagnostic work. In my job I often have clients install it so that we can review their datafiles and diagnose load problems. Many of my calls sound like this. (On Zoom) Me: Okay, so I understand this file is not loading, can you show me the file? Client: (opens file) Me: Ok, hard to see what's wrong at a glance. Can you open the file in Notepad++ for me? Client: (Reopens file in N++) Me: Ah, here we go. You see those characters in blue on line 49? Those are non-ASCII characters. You've got some garbage in there. NULLs, control characters, or some other thing. Those will break the XML parser. Try removing them and reloading the file. Or: Me: So it looks like this is coming from your source system with no line endings, and is quite difficult to read. Can you download the plug-in XML Tools/JSON Tools/Poor Man's TSQL Formatter and let's see if we can get the files indented to make reviewing easier? Or: Me: So if you click on the "View" tab and show the line-endings...thank you. This file is coming over with Windows CRLF line endings instead of the expected LF endings on UNIX/Linux. It's probably throwing off the record parser by one byte for each row. You can use the tool under 'EDIT' to change the newlines to UNIX convention, and you should be good to go. Small things like that. It's a heck of a lot easier to teach the client to do that rather than try to convince them to run dos2unix on a terminal.