Hi Garry, I think that you are right far a long. I'm mostly using XMLports for simpler exports. When it comes to imports, then they are often not flexible enough. I am mostly using the dotnet XML controls for importing, which gives me all the flexibility I need. With NAV 2018/Extensions/VSCode, most of these functions have even become "native" to AL. In the way of design/mapping, then the XMLport object is really just a "modernization" of the old DataPort object, which died with the RoleTailored client. It's "clumsy"-ness is just a sign of that I think. Personally I have never really missed any additional functionality, when we have both options. Don't think that it is a fallback to use a codeunit. But going forward then I'm sure that the Data Exchange Framework will replace both a lot of code and XMLports, when it comes to handling XML files. The DEF may take a bit of time getting familiar with, but once you are, then it's a great tool for handling all kinds of XML (or text) file imports and exports. Have you looked at this?
↧