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
Reporting in NAV 2013 R2 with different builds
Capone
Member Posts: 125
Hi!
Maybe someone has posted something about this but I haven't found anything on the subject.
When 2009 came we had to manage different builds and many decided to have both the production and development environment at the customer site in order to skip maintaining all the different builds in-house. This is practical since many customers run different builds and in some scenarios you can't mix objects and clients to a lower build.
This is a minor hazzle but in combination with the new reporting were you need Microsoft Visual Studio 2012 Professional, Premium, or Ultimate to fully design the reports it suddenly becomes a bigger hazzle.
This leaves us to following options, maintain all the different customer builds in-house or install Microsoft Visual Studio 2012 Professional, Premium, or Ultimate at customer site (which is not really an options because of licensing).
What are your thoughts on this?
Maybe someone has posted something about this but I haven't found anything on the subject.
Source: http://rsdynamicsnavblog.wordpress.com/2013/09/06/nav2013r2-no-need-for-visual-studio-report-builder-supported/“NAV 2013R2 RDLC Reporting Testing – Visual Studio 2012 is not required but suggested for complex reports, SQL Server Report Builder 3.0 is now supported (with limitations!), you “can not use” Visual Studio 2012 Express Releases with integrated shell 2012.”
When 2009 came we had to manage different builds and many decided to have both the production and development environment at the customer site in order to skip maintaining all the different builds in-house. This is practical since many customers run different builds and in some scenarios you can't mix objects and clients to a lower build.
This is a minor hazzle but in combination with the new reporting were you need Microsoft Visual Studio 2012 Professional, Premium, or Ultimate to fully design the reports it suddenly becomes a bigger hazzle.
This leaves us to following options, maintain all the different customer builds in-house or install Microsoft Visual Studio 2012 Professional, Premium, or Ultimate at customer site (which is not really an options because of licensing).
What are your thoughts on this?
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