Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
RTC XMLPort Error - Cannot process node
bob_up
Member Posts: 155
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
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
0
Comments
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 ?
http://support.microsoft.com/kb/2656819
Can anyone please help?
Linkedin Profile: http://in.linkedin.com/in/dhanrajbansal
The workaround is to run this function through Report.