Report upgrade
Rob_Hansen
Member Posts: 296
I need to find out if there's a way to handle this scenario (beyond manually recreating the report). We're upgrading a client from V5 to NAV 2013 R2. We have a rather simple report to upgrade (simple layout). Our approach has been:
- export the report object
- import to NAV 2009 and create layout suggestion (which actually works fine because this one is so simple)
- export the report object
- import to NAV 2013
Here's where the problem hits. We can't upgrade the report as it comes in uncompiled so you get the error that it must be compiled first. When trying to compile, there is an error on a function call with the wrong number of parameters (presumably a base NAV function has had the number of parameters changed) but there's no way to see the actual code that's erroring out...you just see the error message and that's it.
Is there a way to continue in this scenario, or are we stuck manually recreating the report?
- export the report object
- import to NAV 2009 and create layout suggestion (which actually works fine because this one is so simple)
- export the report object
- import to NAV 2013
Here's where the problem hits. We can't upgrade the report as it comes in uncompiled so you get the error that it must be compiled first. When trying to compile, there is an error on a function call with the wrong number of parameters (presumably a base NAV function has had the number of parameters changed) but there's no way to see the actual code that's erroring out...you just see the error message and that's it.
Is there a way to continue in this scenario, or are we stuck manually recreating the report?
Rob Hansen
http://www.epimatic.com
http://www.epimatic.com
0
Comments
-
Did you run the text upgrade on the report before importing into 2013? Also if you design the report and try save it should point to the error.Few years ago we were not existing and few years to come we would be in the grave! So what will benefit us in the grave?0
-
You can comment out all the code using curly braces in NAV 2009 before exporting as text then remove the curly braces after importing in NAV 2013.Joseph Gress0
-
Hi Joseph - Yes, that's what I ended up doing once I used my brain and thought about it.
This report was fine as there wasn't much code...it would be a bit of a pain in a report with significant amounts of code/functions. Thanks for suggesting something here...silly that I hadn't thought of that in the first place. Rob Hansen
http://www.epimatic.com0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions