web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

error after merging

(0) ShareShare
ReportReport
Posted on by 2,390

I have merged codeunit objects from Nav 4 to nav 15 .I am getting following error while importing.

---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
Use the symbol { to start the comment. For example: {Ordinary comment}.
---------------------------
OK
---------------------------

There are lots of opening braces '{' and closing braces '}' . I don't know if it is because of unequal opening and closing braces . please help how to figure out this error.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    keoma Profile Picture
    32,729 on at

    did you follow the upgrade path nav 4 --> nav 2013 --> nav 2015 ?

    first check, if the nav objects you have problems with do compile (by clicking F11) in nav 4 and nav 2013. also export the problematic nav object as text file and reimport it in nav 4, then compile. do you get then an error message?

    then check, if each opening bracket has a closing bracket, each closing bracket has a opening bracket.

    you could also remove all code, which was commented out by curly brackets, also all comments.

    you could replace the curly comments by // in all lines between starting and ending bracket. 

  • NavTech Profile Picture
    2,390 on at

    I have merged from Nav 4 to 15 directly . only some objects are giving errors . i tried deleting all the comments and checked all the opening closing braces all are proper. error is always showing for last line of the file.

  • Suggested answer
    keoma Profile Picture
    32,729 on at

    did you export/import the codeunits as textfile? please try that. then try to compile the codeunits. are these braces also used in other positions, eg. text variables?

  • Suggested answer
    Jens Glathe Profile Picture
    6,092 on at

    Hi NavTech,

    Try single object files. This is annoying, I know. But if you don't have a line number in your complete object file, you're stuffed. You can also try bisection, that was the way I went a few times with especially hard to track errors. It was within one object, though. But it should work with multiple objects in one file, too.

    Regarding bracket pairs: Notepad++ has a nice feature that highlights the bracket pairs. This is for the point where you have tracked down the offending object.

    Going directly from NAV4 to NAV2015 in one merge is one hell of a step, though. With a lot of additional issues. I hope you have only a few modified objects, and very few of them tables with redesigned (standard) fields, or reports.

    with best regards

    Jens

  • rsaritzky Profile Picture
    on at

    If you send me your email address (send through contacts/messages) and would be willing to send me one of your objects in NAV40 format (text file) and your merged NAV2015 file, I'd be happy to troubleshoot this and tell you what the cause was.  Then you can apply it to the rest of your objects.  

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans