New Statement of Directions: Where is NAV '7' going to

Waldo

For a better edited version of this article, please go to the "Source"

It's been a while since I have been posting my blogs here .. but I couldn't resist to put this one on mibuso as well ... just a matter of "being searchable" for you ... and the topic is quite cool 8) .

When you read the document (which partners can download here), you'll notice that everything that's in it, is "what they are focusing on", which means they will try to get in the next release, but every topic is subject to be removed from the scope. This seems obvious to me, really. This is common sense. There isn't a definite release date for NAV '7' (which is a codename) yet, and why and how would they be able to clearly say what's definitely going to be in it?
So, read this article as: they are putting every effort in getting this into the next release, but it could be that it's not going to make it... .
Welcome to the "Statement of Directions" :-).
If you read through the document, you'll find there is a lot they are focusing on. As I'm not really into the functional part of NAV, you have to excuse me that the things I'm going to mention, could not make sense to you, as they definitely make not much sense to me either ;°)
It's a good thing Microsoft still focuses on the right things:
- Simplicity
- Productivity
- Interaction with Microsoft Technology
- User Experience
- Rapid Time-to-Value
This doesn't say much to you, does it? Well, I will try to go into a more concrete level. Here we go:
On functional level:
- Connect with Dynamics ERP. I don't know if you ever heard about it. You can see it as some kind of cloud services. Dynamics NAV will connect with the cloud services that Microsoft is going to build. More about this when more about this is available [;)].
- Financial management. People are going to put a lot of work into:
○ creating a solid foundation on which to build and deliver environmental management accounting and compliance capabilities.
○ enhancing electronic Payments
○ creating electronic Invoicing
○ ...
- For Sales & Marketing it seems that the most important new thing is going to be a "NAV-CRM Connector". I hear you know thinking "FINALLY" :-). Not unimportant: you're going to be able to extend this connector.
- What about Service Management? It's clear that in general, they will focus on a closer integration with other application areas such as Jobs, Resource mgt, Warehouse, Distribution and MS Dynamics CRM (via the connector)
- The Manufacturing-granule is also something they are going to put a lot of work in in following areas:
○ Production planning overview
○ Tracking and analyzing of plans,
○ Prioritization
○ Subcontracting
○ Integration with the job module
--> one planning for all resources
○ Increased client extensibility and visualization capabilities (is that a visual planning?)
- On top of these functional areas, there will be some improvements in these as well .. where I'm not going into detail (because I was bored with the functional stuff, and wanted to get into the technical stuff [;)] - there wasn't much more, believe me .. just read the document):
○ Warehouse & Distribution
○ Jobs and Project Management
○ Resource Management
○ Business Intelligence
On Partner productivity (which is mostly "Technically Speaking"):
- Improvements to the Page Designer.
○ More graphical page designer. When I read this, I guess there is going to be some kind of preview or whatever. Something where you can clearly see what consequences will a particular change have on a page (visually).
- Discontinuation of forms. This is stated more then once in the document, so I really think this is a strong focus of the development team. This also means many things:
○ You'll HAVE to go RoleTailored
○ You'll HAVE to go on SQL Server
○ ...
- Ability to debug on the NAV Server in C/AL. Is this a new debugger? Yep, it is! And this one is going to show you the C/AL code, not the C#.
- MS Dynamics Sharepoint Integration Framework. This can mean a lot of different things. But let's just think they're going to create a framework where it's possible to publishe pages into a sharepoint web part ;°).
- Adminstration from within the RTC. Now, it's not possible to e.g. Create users within the RTC. You have to use the classic for that. They will put a focus on "not having to do that anymore".
- .NET interoperability: allowing .NET to be accessed from C/AL. Now, isn't THAT cool?
- Query designer. Now, Finally: Now, building a report meant, building a data set, then, building a RDLC. But what if I want to reuse that dataset? Or what if something changes? Multiple datasets had to changes. In next release: they will try to create a query which you can use for multiple reports. On top of this, you will get a RDLC-wizard. This is less useful in my opinion, because RDLC is quite easy to do.
- Improved client extensibility: Easy deployment. I also hope it's going to be able to use events. THAT would be nice :-).
So, what about User productivity:
- Improved integration with sharepoint is obviously a very important part of "user productivity".
- Extend integration with office 2010
○ Timesheet mgt
○ Customer report generator
- Support for unified communication. Cool. Although I don't have customers yet that use UC ... .
- Easier reporting for customers by SSRS & Report Builder. Are they going to foresee something in this Area?
- Ability for ad hoc reporting in Excel. Hm. And what about JetReports? Is it going to be useful after this?
- More charts and KPI's.
- Improved page layout options and other enhancements that make it easier for the user to enter and view data. Whatever that's going to be....
Other Technical Improvements. Not unimportant and definitely worth mentioning:
- No support for C/SIDE Databases. Isn't that a bitch? That means: guys, get yourself migrated to SQL Server!
- Support to easily consume web services. True. Consuming web services still is a b***h. Apparently, they're working on a solution :-).
- Improved integration with outlook (large synchronizations would go easier and faster)
- 64 bit service tier. On word: YES! :-).
So, dibbededibbede, that's all, folks. That's all I would like to share with you concerning the SOD. Again, there are NO PROMISES. There are FOCUS points. And if you ask me: there is a LOT to look forward to, so Microsoft, keep up the good work, and try the get everything in [:)]!
For partners, it's always a good idea to follow the focus and strategy of Microsoft. For example, don't go building you own solution to consume web services, or at least, don't put too much work in it, because Microsoft is going to provide you a solution ... or at least ... is probably going to provide you one. Now you know the strategy and directions of Microsoft, so try to build your own strategy around it: the discontinuation of forms and no support for native databases are quite clear points in this.. .
Enjoy!

ara3n

Improved client extensibility: Easy deployment. I also hope it's going to be able to use events. THAT would be nice

Client extensibility = Addins? If yes, then It already has events.

Waldo

You're right... :oops:
I didn't play with this myself .. yet

davmac1

NAV 8 will make all the .net developers amongst us happy.
Looks like we will need to know C# for future releases.
If I read this correctly, they are dropping forms in release 7. Does this mean no more classic client? (And no more heads down data entry?)

ara3n

davmac1 wrote:

NAV 8 will make all the .net developers amongst us happy.
Looks like we will need to know C# for future releases.
If I read this correctly, they are dropping forms in release 7. Does this mean no more classic client? (And no more heads down data entry?)

There will be a classic client but just for development purposes.

I didn't read anywhere that for Nav 8 you'll need t know c#

kine

For me it is logical step to stop support both technologies (RTC and Classic client). But you see too much behind this. May be that it is just about the variant, that new application will have only pages and not form to not be bound with the transformation tools and be able to use all features of the new client. But I think that there will be nobody who will try to "remove" form presentation part of the classic runtime... but it is just a guess...

Marije_Brummel

1. Shipping an application with no forms does not mean that the classic client is no longer able to run forms.

2. We are definately not moving to c#

This is how roumours start...

tabularasa

What about Visual Basic. The Reports in RTC in visual Studio seem to be coded in Visual Basic.

ara3n

only the basic logic on displaying something.
Knowing a couple of functions and how to write an if statement would be sufficient.

Miklos_Hollender

Waldo wrote:

because RDLC is quite easy to do

Thanks, good joke.

Nothing can be easier than displaying 20 sections nested in 6 levels of hierarchy which was matrix-multiplicated into a flat datastructure.

Belias

Waldo wrote:

because RDLC is quite easy to do

they are NOT easy they're hard and sometimes also time consuming!!
you can say they're powerful, but their learning curve is really steep, i really hope that MS will make their development less bloody..

Miklos Hollender wrote:

Nothing can be easier than displaying 20 sections nested in 6 levels of hierarchy which was matrix-multiplicated into a flat datastructure.

:shock: if you've done it, congrats...i'd like to see at least a printscreen of the rdlc layout...
that said, i think it was hard to do it in classic client, too...