Upgrade from 16 to 17

(0) Share

Report

Posted on by Andreas Panayiotou

Hi,

Recently we have upgrade from 2016 to 2017 . Oddly enough the upgrade of data and application code was successfully took place in an Azure machine but the interface remained the 16's one. What did go wrong in this case?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

Mohana Yadav 60,977 Super User 2025 Season 2 on at

Like (0)

Report

RE: Upgrade from 16 to 17

do you mean by Interface? Windows client?

did you update your clickonce and installed on all machines?

Was this reply helpful? Yes No
Andreas Panayiotou 27 on at

Like (0)

Report

RE: Upgrade from 16 to 17

It is like i have 2016 version.. The interface is 2016 but my nav client is 2017.

Was this reply helpful? Yes No
Tharanga Chandrasekara 23,118 on at

Like (0)

Report

RE: Upgrade from 16 to 17

If you are talking about NAV windows client, then NAV 2016 and NAV 2017 interface is almost same. There is not much of a different. Please correct me if you are referring to something else.

Was this reply helpful? Yes No
Verified answer

Andreas Panayiotou 27 on at

Like (0)

Report

RE: Upgrade from 16 to 17

Hi Tharanga,

We upgraded the db but the objects are 2016 thas why we cant see new interface. We need to merge them with the new ones so we see the new interface .

Was this reply helpful? Yes No
Suggested answer

Tharanga Chandrasekara 23,118 on at

Like (0)

Report

RE: Upgrade from 16 to 17

Hi,

I thought you already merge objects during the upgrade. Glad you found the issue.

Was this reply helpful? Yes No
Suggested answer

Amol Salvi 18,698 on at

Like (0)

Report

RE: Upgrade from 16 to 17

You did only platform upgrade and not the application upgrade .You need to do the merging of object

msdn.microsoft.com/.../dn271652(v=nav.90).aspx

Was this reply helpful? Yes No