Options

RTC XMLPort Error - Cannot process node

bob_upbob_up Member Posts: 155
edited 2015-08-08 in NAV Three Tier
I have created an xmlport which is used in a soap request to a 3rd party webservice. This works fine in the classic client but if I try to perform the same process in RTC I get the message "Could not process node s:Envelope", which is my root node.

I see there is a hotfix http://support.microsoft.com/kb/2656819 for a similar-sounding issue but it is version 6.0.33046 and I am on version 6.0.33597. Am I right in thinking that means I must already have that fix ?

My XMLport structure is shown below.




17/9/12

I have now tried the following, and I still have the problem :

1. I have installed the hotfix described above
2. I have removed the s: prefix from the Envelope and Body nodes
3. I have set the "Direction" property to "Export" on the XMLport (because another post I have read).
4. I have changed the UseDefaultNamespace property to "Yes".
5. I have removed the namespace attribute from the Envelope node (clutching at straws ](*,) )

Just to confirm, works fine in the Classic client in its original form.

27/9/12

I have now given up searching for a solution and am planning to write directly to the file, dispensing with the XMLport. Seems crazy but I just cant get the XMLport to behave in the way I need it to in the RTC (the way it does in the Classic client).

Bob

Comments

  • Options
    bob_upbob_up Member Posts: 155
    I have now tried the following, and I still have the problem :

    1. I have installed the hotfix described above
    2. I have removed the s: prefix from the Envelope and Body nodes
    3. I have set the "Direction" property to "Export" on the XMLport (because another post I have read).
    4. I have changed the UseDefaultNamespace property to "Yes".
    5. I have removed the namespace attribute from the Envelope node (clutching at straws ](*,) )

    Just to confirm, works fine in the Classic client in its original form.

    Has anyone got anything else I can try ?
  • Options
    DRBDRB Member Posts: 105
    I am also facing this issue and the hotfix mentioned on following link didn't resolve this issue:

    http://support.microsoft.com/kb/2656819

    Can anyone please help?
    -Dhan Raj Bansal
    Linkedin Profile: http://in.linkedin.com/in/dhanrajbansal
  • Options
    VanDoghVanDogh Member Posts: 8
    We run into this issue.

    The workaround is to run this function through Report.
Sign In or Register to comment.