Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
xml via automation in codeunits without xmlports
davmac1
Member Posts: 1,283
I am upgrading NAV2009 to NAV2013R2.
I am running into a problem with the xml code executed directly in the codeunits.
I get the automation variable not instantiated when it first executes “XMLNode := XMLDom.selectSingleNode”
If I add a create(XMLDom) before it, it compiles, but gets a different error – cannot create an instance of an automation server.
I added a create on the document (CREATE(XMLDocument, TRUE ,TRUE);) ('Microsoft XML, v6.0'.DOMDocument60) which does not get an error. In NAV2013R2 am I meant to tie all this together somehow>
The code is currently using:
'Microsoft XML, v6.0'.IXMLDOMAttribute
'Microsoft XML, v6.0'.IXMLDOMNode
It does look like this automation should still be supported in the new NAV versions based on the online documentation.
Is there a way to get it to work, or would I be better off switching to dotnet?
Problem was different automation names in Windows server - had to make sure all old document definitions were changed correctly to DOMDocument60.
I am running into a problem with the xml code executed directly in the codeunits.
I get the automation variable not instantiated when it first executes “XMLNode := XMLDom.selectSingleNode”
If I add a create(XMLDom) before it, it compiles, but gets a different error – cannot create an instance of an automation server.
I added a create on the document (CREATE(XMLDocument, TRUE ,TRUE);) ('Microsoft XML, v6.0'.DOMDocument60) which does not get an error. In NAV2013R2 am I meant to tie all this together somehow>
The code is currently using:
'Microsoft XML, v6.0'.IXMLDOMAttribute
'Microsoft XML, v6.0'.IXMLDOMNode
It does look like this automation should still be supported in the new NAV versions based on the online documentation.
Is there a way to get it to work, or would I be better off switching to dotnet?
Problem was different automation names in Windows server - had to make sure all old document definitions were changed correctly to DOMDocument60.
David Machanick
http://mibuso.com/blogs/davidmachanick/
http://mibuso.com/blogs/davidmachanick/
0
Answers
You can find one called Mircosoft.MSXML in Dotnet and that should mostly fit with you existing function.