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
- 304 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
Report with no RLDC layout in RTC gives Not Valid date error
ymgrigsb
Member Posts: 2
We are transitioning from Classic to RTC in Navision 2009R2. Our servers are at version 6.00.32146.0. We are trying to run Classic only reports in the RTC client and then as we get time, upgrade the reports to RTC reports. We removed all the RDLC layouts from the reports. When we run a classic only report in RTC on this version, we get the error "2015-08-25T00:00:00-04:00 is not a valid date". If we use an older RTC client version (6.00.32012.0), the classic-only report runs in RTC without error.
We would just use the older client version EXCEPT that we are wanting to allow users to be able to go back to the Classic client version if they run into issues with RTC while trying to do their job (until we get all the RTC functionality debugged and verified). Adding an RDLC layout to a report causes the older (6.00.32012) Classic client to crash. The newer Classic client runs fine with the added RDLC layout in a report.
We would prefer just to use the newer versions of the RTC and Classic clients (our users are on the old client currently because most are still using Classic). Is there a way to fix the invalid date error on the 6.00.32146.0 version RTC client for classic only reports? If we could fix this, then we could have the ability for the users to switch back and forth for both classic only and RDLC layout reports while we progress with our upgrade.
Thanks for your help!
We would just use the older client version EXCEPT that we are wanting to allow users to be able to go back to the Classic client version if they run into issues with RTC while trying to do their job (until we get all the RTC functionality debugged and verified). Adding an RDLC layout to a report causes the older (6.00.32012) Classic client to crash. The newer Classic client runs fine with the added RDLC layout in a report.
We would prefer just to use the newer versions of the RTC and Classic clients (our users are on the old client currently because most are still using Classic). Is there a way to fix the invalid date error on the 6.00.32146.0 version RTC client for classic only reports? If we could fix this, then we could have the ability for the users to switch back and forth for both classic only and RDLC layout reports while we progress with our upgrade.
Thanks for your help!
0