That's part of my problem with them, Microsoft have imposed limitations that don't exist in XML that make them significantly more difficult to work with than they should be, for example I'm doing a Shipping Agent integration, it's an XML file transfer basically output an XML file, wait for the response then import 2 fields from the response... sounds very simple. the Export works perfectly as I'd expect, exports are generally pretty good with XML ports. the import however, there are thousands of potential fields in the schema so it is not realistic to replicate the entire schema (especially when I'd do all that work then hit a deal breaker that stops me being able to use it) If there's an error then The Error node is included otherwise you get a Shipment details node, there is no combination of MinOccur, MaxOccur and UseLax that allows this schema to be processed, whatever options are chosen it'll fail on either an error or a successfully processed document. these aren't restrictions in XML it's just some self imposed limitations in XML Ports. another example, we receive XML order files from customers, some customers send through the elements in a slightly different order, which again is perfectly reasonable with XML, but there's no way to handle this in an XML port, in NAV 09 there was a messy work around where you could add an element in every position it might appear with minoccur set to 0 and it'd handle it, that seems to have disappeared with later versions. XML Ports just seem to strip away a lot of the flexibility that makes XML so useful and only allows for importing of very strict/static XML files... i.e. it's not extensible anymore.
↧