Small and medium business | Business Central, N...

Upgrade from NAV 2013 R2 to NAV 2017

(0) Share

Report

Posted on by Ankit7859

Hi All,

I have been facing some "Parsing" issues while upgrading NAV 2013 R2 to NAV 2017 using NAV merge tool. It is creating few(1000) objects in RESULT folder before the error is thrown.

2313.Error.JPG

When i check the caption with Error in my file, it does not have any special character like the way it is showing in Error screen however when i remove this caption then error moves to next pointer and throws same error.

Our customized version is NAV 2013 R2 W1 with Chinese Localization pack above W1.

Following the Microsoft documents for upgrades, i have taken three different versions as below:

Original: NAV 2013 R2 W1

Customized: Our NAV 2013 R2 W1 with Chinese Localizations

Target: NAV 2017 CU15

To get rid of this Error, I then tried to remove the Chinese captions from my customized objects using "Remove-NAVApplicationObjectLanguage" command so that i could import it back after merging but it throws the same error of Parsing.

Did anyone face this issue earlier or am i missing something?

Thank you in advance!!

All responses (2)

Answers (0)

Ankit7859 40 on at

Like (0)

Report

RE: Upgrade from NAV 2013 R2 to NAV 2017

Thank you Gearoid for your reply.

It seems this command parameter is not available in NAV 2013 R2 and throws below error:

"The program property 'unicode' is unknown.

The manual Installation and System Management contains a list of the correct program properties."

It is working in NAV 2017 which i tried and opens up the developer environment.
Suggested answer

Gearoid on at

Like (0)

Report

RE: Upgrade from NAV 2013 R2 to NAV 2017

Hi,

It's a bit of a long shot but you could try compiling the relevant objects using finsql.exe running with the following command line parameter: Unicode=1

Using “Unicode=1” with finsql.exe should cause NAV to compile captions interpreting caption values with the language associated with the CaptionML property (rather than using the "language for non-unicode programs" which is configured on the local machine).

If that does not work then I would recommend opening a support ticket with your Dynamics NAV localization partner or Solution Provider.