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
- 305 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
Export to Excel from VAT transact.: Problems with some data
Magfo
Member Posts: 11
I've found a problem related to exporting data from NAV to Excel. There are some workarounds and other ways of finding an answer, but in my case we've got problems with that, due to restrictions in accessing the customer server. Long story short:
We're trying to export VAT-transactions from the VAT-transaction list in order to analyze some things in Excel. When we do that we get an error ("Table"), which stops the export without data. That problem isn't uncommon, I've searched the forums and seen some variants of it.
In this case I can track the error to an document number being set to "2010-12". (Error log file)
It seems that Excel gets confused with that format, since it regards it as a number, which turns into a formula since there's a "-" sign. A pure number or a pure text string works fine (ie: 2133, V1-14, TEST etc), but with something like the above we get a crasch instead.
The question then becomes: Has anyone got a nice solution to this problem? Is there one?
Normally we'd be able to help the customer somehow, by working around the issue. This time the customer sits behind extra high security protection, which essentially means that all form of external connection is void, and a visit is needed for any kind of more advanced change in code. Which of course shouldn't be a problem, except it involves 6h of travel to get it done... (Don't ask
)
I guess I'm wishing for the impossible! I'd settle for a good explanation why this isn't working out of the box...
We're trying to export VAT-transactions from the VAT-transaction list in order to analyze some things in Excel. When we do that we get an error ("Table"), which stops the export without data. That problem isn't uncommon, I've searched the forums and seen some variants of it.
In this case I can track the error to an document number being set to "2010-12". (Error log file)
It seems that Excel gets confused with that format, since it regards it as a number, which turns into a formula since there's a "-" sign. A pure number or a pure text string works fine (ie: 2133, V1-14, TEST etc), but with something like the above we get a crasch instead.
The question then becomes: Has anyone got a nice solution to this problem? Is there one?
Normally we'd be able to help the customer somehow, by working around the issue. This time the customer sits behind extra high security protection, which essentially means that all form of external connection is void, and a visit is needed for any kind of more advanced change in code. Which of course shouldn't be a problem, except it involves 6h of travel to get it done... (Don't ask
)I guess I'm wishing for the impossible! I'd settle for a good explanation why this isn't working out of the box...
0