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
Technical Upgrade - The file that you are importing is not based on the RDL 2010 schema.
Tomigs
Member Posts: 86
Hi,
I'm running a technical upgrade from NAV2017 database to BC14 (on premises).
I've prepared the database, compiling all the objects, etc.
When I finally open the NAV2017 database with the BC14 development environment, after some hours of work updating it, it shows the error:
The file that you are importing is not based on the RDL 2010 schema.
You must upgrade it to the RDL 2010 schema.
Do you know what it can be? Is it maybe one faulty report? If so, any suggestion on how could I identify it? All of them are compiling.
I see some threads point to different SQL versions, but I'm doing the upgrade using the same database server as the NAV2017 database.
Thanks
Tomas
I'm running a technical upgrade from NAV2017 database to BC14 (on premises).
I've prepared the database, compiling all the objects, etc.
When I finally open the NAV2017 database with the BC14 development environment, after some hours of work updating it, it shows the error:
The file that you are importing is not based on the RDL 2010 schema.
You must upgrade it to the RDL 2010 schema.
Do you know what it can be? Is it maybe one faulty report? If so, any suggestion on how could I identify it? All of them are compiling.
I see some threads point to different SQL versions, but I'm doing the upgrade using the same database server as the NAV2017 database.
Thanks
Tomas
0