Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics NAV forum / Upgrade from NAV 2013 ...
Microsoft Dynamics NAV forum
Suggested answer

Upgrade from NAV 2013 R2 to NAV 2017

(0) ShareShare
ReportReport
Posted on by Ankit7859 40

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!!

Categories:
Other
Upgrade
  • Ankit7859 Profile Picture
    Ankit7859 40 on at
    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 Profile Picture
    Gearoid on at
    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

more Community News

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,532 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,501 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans