NAV TechDays 2014: The new Paradigm of NAV Upgrade Story

Administrator

NAV TechDays 2014: The new Paradigm of NAV Upgrade Story
Presentation during the NAV TechDays 2014 conference of 20 & 21 November 2014 in Antwerp (Belgium)

Presenters: Anca-Roxana Ciocan, Bas Graaf, Aida Seifi Labrosse

Presented on Friday 21 November 2014, 11:00 - 12:30

http://www.mibuso.com/dlinfo.asp?FileID=1613

Discuss this download here.

chrisdf

Hi,

This was a great presentation and helps a lot with the upgrade story. I took the presentation and tried to use it to upgrade our bespoke application to Cumulative upgrade 2 - it was previously upgraded to Cumulative Upgrade 1.

I am struggling with the "ugly" that is version control. Your slide takes into account a "simple" upgrade from RTM to CU1 and I can see how this works but when we have the following scenario where the application has already been through one upgrade scenario and country localisations are in place. These are some of the things that are going wrong:

1. In CU2 there are already objects that have been upgraded in CU1 but they are included in the cumulative 2 rollup and not modified but do have a country localisation.
Target = NAVW18.00.00.38457,NAVGB8.00.00.38457
Modified = NAVW18.00.00.38457,NAVGB8.00.00.38457
Result = NAVW18.00.00.38457,NAVGB8.00.00.38457,NAVVGB8.00.00.38457
Clearly the routine repeats the second string from the localisation.

2. When there is a version control from my application
Target = NAVW18.00,NAVGB8.00,DD7.00
Modified = NAVW18.00.00.38798,NAVGB8.00.00.38798
Result = NAVW18.00.00.38798,NAVGB8.00.00.38798,NAVGB8.00,DD7.00
In the above example an erroneous NAVGB8.00 is added to the result string.

Do you have any different versions of your powershell script to handle version numbers that would take care of this issue?


The second problem I have when following your script is with one of the commands you demonstrated to get the objects from the source database:

<Export-NAVApplicationObject DynamicsNAV80 .\Original\rtm.txt>

When I try this on a Cronus database I keep getting presented with a Login failure - even if I add myself as a user to the Cronus database and in SQL - I am using a Windows log-in maybe it doesn't work with that?

Export-NAVApplicationObject : : [22922070] The following SQL Server error or errors occurred:
18456,"28000",[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user <Windows User name>

Any ideas greatly appreciated !

basgraaf

Hi Chris,

I've posted a more advanced function for merging version lists on the NAV team blog. I think it supports the scenarios you mention. For each "product code" (to be passed in) it only returns the version with the highest number.

The export command works for Windows logins. Is the database attached to the default instance on the local host? If not, you'll need to provide more information to the command.

Kind regards,
Bas