NAV 2009 R2 - HotFix For XMLPort Flat File Bug?

OldNavDog

Hi Experts,

I need to fire-off an XMLPort under 2009 R2 CLASSIC (actually, under a NAS, but same thing), but unfortunately, for some unexplainable reason, the XMLPort Object IGNORES the "Format" Property, and ALWAYS acts as if it is set to "XML". So you can't use it for "Flat-Files".

Curiously enough, if you Run the same XMLPort under the Role-Tailored Client, it works FINE.

So, has anybody else here experienced this, and (even better), know of a workaround (that doesn't involve the RTC or Webservices), or a HotFix that addresses this issue?

And since I really need this to work under a NAS, I CANNOT use a Dataport. Those CANNOT be launched under a NAS.


Thanks In Advance,

pjotresztick

According to me, the parameters that were newly added in NAV2009 in the XMLPort are only working for the RTC (see: https://msdn.microsoft.com/en-us/library/dd338608.aspx). The NAS of NAV2009 is based on the classic approach.

Probably the best thing to do is to create a report or codeunit and code your import/export so it can process flat files.

OldNavDog

LOL! Probably shoulda mentioned: Been there, done that. In fact, so often that I now OWN the T-Shirt FACTORY!!! ;-)

Wanted a more, um, "Civilized" fix, like a MS HotFix.

But thanx for trying...

jglathe

Hi OldNavDog,

Microsoft doesn't support this version anymore... whatever that means. And yes, "Dataport" functionality of XML ports don't work in Classic Client. You could invoke the thing via Web Service, though... but it is workaround after workaround after workaround And it only works when you have a NST running. Oh, and it isn't a NAS, too, but I think you could execute a program from NAS.

with best regards

Jens

OldNavDog

I actually had the Webservices kludge bit working at one point, using a modification I pieced together from the technique used to run multiple Job Queues from one NAS; but I could never get it to work at the Client's site. And yes, I had an NST and the WS Services both up and running.

I just am so lame with SOAP and Webservices in general that I don't even know which way to start with debugging same. And it doesn't help that debugging through the entire WS "handoff" is basically impossible, or at least I don't know how to do it.

jglathe

OldNavDog wrote: »

I just am so lame with SOAP and Webservices in general that I don't even know which way to start with debugging same. And it doesn't help that debugging through the entire WS "handoff" is basically impossible, or at least I don't know how to do it.

Oh that's easy: You can't. I mean, when you're not Microsoft. If the XMLPort is working, though, you could verify the rest of the code by just using something else. That's what we did... But it is a workaround-fest, yes.

OldNavDog

The XMLPort IS working. I will have to create the error again to see exactly what it was whining about. Sounds like if I did that, perhaps you could help... ;-)