5.0 Upgrade Toolkit is available

Waldo

I just got the message that the 5.0 Upgrade Toolkit is available on partnersource:

https://mbs.microsoft.com/partnersource/downloads/releases/microsoftdynamicsnav50.htm?printpage=false

ara3n

That's great.
The question now is would you upgrade to 5.0 or wait for Q1 2k8 to upgrade to 5.1


If I were a company, it would would for 5.1.

Alex_Chow

ara3n wrote:

That's great.
The question now is would you upgrade to 5.0 or wait for Q1 2k8 to upgrade to 5.1


If I were a company, it would would for 5.1.

Isn't the only change between 5.0 and 5.1 the executables? :shock:

Oh wait, I forgot everything is subject to change without notice... :roll:

ara3n

It's not just the executable, but all the other technology that comes with it.
webservice, 3 tierd, reporting services,new client.

I wouldn't upgrade now, because just an update takes a couple of months. By that time 5.1 will be out.

Waldo

Well, officially, you should first move to 5.0, then to 5.1 ... .

<edit>
the download is now also available on mibuso:
http://www.mibuso.com/dlinfo.asp?FileID=878

mart1n0

Ok that's nice, but I need the Upgrade Toolkit for Switzerland.

Anybody has any idea when this one will be available?

Waldo

I think you can contact your local product manager for that... .

Nikk

I recently carried out a manual upgrade to version 5 for a small projects database..went ok except that the security tables /structures between ver 3.60 and 5.0 have differences.

Nice to finally obtain it.

Marije_Brummel

ara3n wrote:

That's great.
The question now is would you upgrade to 5.0 or wait for Q1 2k8 to upgrade to 5.1


If I were a company, it would would for 5.1.

Please read my blog as to why upgrade to 5.0.

http://dynamicsuser.net/blogs/mark_brum ... v-5-0.aspx

When you receive the upgrade toolkit for 5.1 the first step will be

Upgrade your current database to the 5.0 functionality
The second step will be

Migrate to SQL Server

Both these steps can be done today! This way you will spread the risk of a big bang upgrade with all possible mistakes.

You also might want to ask yourself: Do I want to be on the first release of 5.1 or on the most stable version of the Classic client.

Waldo

Thanks for the confirmation .

The SQL migration is indeed something to think about ... in time!
It should be a whole seperate project which should be closed and approved before even thinking about upgrading to 5.1 .

ara3n

You can still use classic client in 5.1.


I would not move to 5.0 on sql. Performance issues is the reason.

My point about not upgrading is the merging of objects.
Specially the forms.
There will of course will be other objects that are fixes after 5.0 is released.
my guess, more than 100.


You have to reinstall all the clients.
retrain the users.

Waldo

Wasn't it like this:

5.0 = functionality
5.1 = user interface

So for me, if a customer wants 5.1 ... it wants the UI ... so he has to move to SQL Server.

True that 5.1 runs on classic client, but then you're just working with 5.0 ... there is nothing different (... but this is off course still theory ...).

I agree that it will be a huge amount of work to move to 5.1 ... .

Marije_Brummel

Performance issues should not anymore be a reason not to move to SQL.

There is enough knowledge, tools and possibilities to get it to work. Waiting will only put you behind.

Problem with this knowledge is to get it to the engineers of the partners. It is a complex theory which not everyone seems to understand.

Also salespeople should adjust the expectations of the enduser to mach reality and create budget for performance tuning if the database tend to be a big one.

The forms changed in 5.1 to mach the pages are not typical forms you will customise at a customer so do not expect much work on that.

Another issue with 5.1 is that it is just not als flexible as the old client. You cannot play with the ui like you are used to. I expect a lot of comotion from the partnerchannel about this and hope that MS will redesign some features after that.

New customers who do not have the experience with the old client have different expectations, but they will have to find all the bug's for MS to solve.

Waldo

That's why we will be focussing on new customers ... as for as customers that want to upgrade ... try to do a new implementation (how was it called again .. cold turkey?) .

David_Cox

If you have a legacy modifed 3.70 database on SQL, running on 3.70 binaries, which will be dropped within 2 years, can you still just do the Navision binary upgrade, and leave the 3.70 database objects as is?

I am asking this as I read somewhere that 3.70 will not run on Vista etc: and at least version 4 is needed, or is that not true?.

David

Waldo

We have done the same for exactly that reason ... with no problems whatsoever. So my answer would be: yes.
Keep in mind, for Vista, my blog could be quite interesting:
http://dynamicsuser.net/blogs/waldo/archive/2007/05/28/dynamics-nav-on-vista.aspx

Alex_Chow

Navision 2.0 will work on Vista.

Version 2.6, 3.0, 3.01, 3.1, 3.6, 3.7, 4.0 sp1 sp2 will not work on Vista.

Luc_VanDyck

mart1n0 wrote:

Ok that's nice, but I need the Upgrade Toolkit for Switzerland.

Anybody has any idea when this one will be available?

The upgrade toolkit for CH 5.0 has been released!