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
Creating classic reports but thinking ahead to RTC
Capone
Member Posts: 125
Godday!
I have been thinking about those customers that still runs on pre RTC versions and that wants new reports.
It doesn't feel good to develop classic reports when you know you have to rewrite most of them when migrating to an RTC version.
How do you deal with this? Do you continue to develop reports or do you try to minimize the migration workload by doing something else then making a new classic report?
My suggestion would be to build reports that exports to excel/word instead by creating a ProcessingOnly report that uses the excel automation objects.
Pros with this solution is that you don't have to rebuild the graphical view of the report which can be very tedius when migrating to RTC.
The cons is that the user needs to have excel installed and that using automation is a bottleneck when it comes to speed but often users don't print tons of pages.
So what do you say or think about the issue?
I have been thinking about those customers that still runs on pre RTC versions and that wants new reports.
It doesn't feel good to develop classic reports when you know you have to rewrite most of them when migrating to an RTC version.
How do you deal with this? Do you continue to develop reports or do you try to minimize the migration workload by doing something else then making a new classic report?
My suggestion would be to build reports that exports to excel/word instead by creating a ProcessingOnly report that uses the excel automation objects.
Pros with this solution is that you don't have to rebuild the graphical view of the report which can be very tedius when migrating to RTC.
The cons is that the user needs to have excel installed and that using automation is a bottleneck when it comes to speed but often users don't print tons of pages.
So what do you say or think about the issue?
Hello IT, have you tried to turn it off and on?
Have you checked the cables?
Have you released the filters?
http://www.navfreak.com
Have you checked the cables?
Have you released the filters?
http://www.navfreak.com
0