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
Conflicts of Report Builder calls NAV 2015 / NAV 2013 R2
Kowa
Member Posts: 923
After having installed NAV 2015 (with brings with it the new report builder from SQL Server 2014 instead of Version 3 which was part of the NAV 2013 R2 installation) it is no longer possible to open the layout of a report in the NAV 2013 R2 Development Environment because this error message pops up.
Has anyone found any means of using the report builders of both environments simultaneously?
Microsoft Dynamics NAV Development Environment
An error occurred when opening the report designer. A supported version of Report Builder could not be found.
Kai Kowalewski
0
Answers
Another solution is to update NAV 2013 R2:
As I just learned, NAV 2013 R2 Cumulative Update 11 (Build 37799) will work with the new Report Builder 3 for SQL Server 2014 (also known as Report Builder 12).
These cross-version and even cross-build conflicts are driving me crazy. I oversee our internal development systems. Prior NAV versions live quite well together. I support NAV 2009 R2 all the way back to NAV version 4 SP3 on the same platforms. But these never versions are creating a real problem. As it seems almost the each new update creates more conflicts.