Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 298 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Rim Tool Excel & NAV schema conflicts
jannestig
Member Posts: 1,000
Just wondering if anyone has noticed this for the XML schemas in different version of office and NAV
In my scenario I have taken a 5.01 with RIM toolkit 2 imported, when i go to export a table to Excel the format (EG i want a setup table for my migration to nav 2009 sp1) It will export the file in *.xl* format but when you go to 2009sp1 looks for the same file it will only search for.XLS files.
The workaround is to change file type in 5x to all files then add the extension .xls which works. (havent tested XML format yet)
But the main issue is this is annoying and should be supported as it is part of their surestep methodology.
it looks like codeunit 8611 is coded to use .xls format only.
Anyone else experianced this ok can confirm
In my scenario I have taken a 5.01 with RIM toolkit 2 imported, when i go to export a table to Excel the format (EG i want a setup table for my migration to nav 2009 sp1) It will export the file in *.xl* format but when you go to 2009sp1 looks for the same file it will only search for.XLS files.
The workaround is to change file type in 5x to all files then add the extension .xls which works. (havent tested XML format yet)
But the main issue is this is annoying and should be supported as it is part of their surestep methodology.
it looks like codeunit 8611 is coded to use .xls format only.
Anyone else experianced this ok can confirm
0