Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Compile Error 2009 R2 ...
Microsoft Dynamics NAV (Archived)

Compile Error 2009 R2 -> 2013 SP1

(0) ShareShare
ReportReport
Posted on by Raphi 180

Hello


I am upgrading a Navision 2009 R2 database to 2013.


Actually, I am at the point where I have to compile the OldCustomVersion_Reports.

Now I got the following errors:

"TableData 2000000003 does not exist" (Report 11516)

"TableData 2000000002 does not exist" (Report 11561, 3010618/628/632/838)

"You have specified an unknown variable. Payment Page 2 Define the variable under 'Global C/AL symbols'." (Report 3010602/606/607/623/624/627)

How can I fix it? Do I have to compile and upgrade them or just export it without compiling and upgrading?

Or can I just "delete" these reports? The reports with 301* are from a tax Addon, I think we don't need it anymore.

Best regards

Raphi

*This post is locked for comments

  • Verified answer
    Mohana Yadav Profile Picture
    Mohana Yadav 59,139 Super User 2024 Season 2 on at
    RE: Compile Error 2009 R2 -> 2013 SP1

    Use Araxis or Beyond Compare.

    You can google wuth 3 way text compare

    www.araxis.com/.../three-way-file-comparison-and-merging.en

  • Raphi Profile Picture
    Raphi 180 on at
    RE: Compile Error 2009 R2 -> 2013 SP1

    thank you.

    Now my (I hope so) last question:

    How can I compare 3 (!) textfiles at the same time? There are more than 2000 files to compare from all 3 databases. I use WinMerge but I can only compare 2 at the same time.. Do you have any tips?

    BR

  • Verified answer
    Mohana Yadav Profile Picture
    Mohana Yadav 59,139 Super User 2024 Season 2 on at
    RE: Compile Error 2009 R2 -> 2013 SP1

    You can export language modules from Tools-->Language Modules-->Export

    Choose Language name German, French and Italian and import in another database and export the objects again and compare.

  • Raphi Profile Picture
    Raphi 180 on at
    RE: Compile Error 2009 R2 -> 2013 SP1

    OK thanks. I will do that :)

    Now another question.

    In the UpgradingNAV2013.pdf manual, there I have the point

    "For each version, split the converted .txt files into single objects and review them using a file comparison tool. Delete the objects that are identical and not customized."

    I tried to compare the oldBaseVersion with the oldCustomVersion with WinMerge. But there are more than 1500 files different! I checked the baseversion and saw that there are only the CaptionML entries different (in my customversion I have german, french and italian). How can I exclude these entries? Do I have to create a new OldBaseVersion? If yes, how do I know, which the correct database is (both environments are W1)? I used the one from the DVD.

    BR

    Raphi

  • Suggested answer
    TharangaC Profile Picture
    TharangaC 23,116 on at
    RE: Compile Error 2009 R2 -> 2013 SP1

    Table 2000000002 and 2000000003 were removed in the 2013 version.

    insted of them you can use the following tables :

    User : 2000000120

    Access Control :2000000053

    Refer below link to see what other tables are been removed in the 2013 version

    msdn.microsoft.com/.../hh997053(v=nav.70).aspx

    As a fix for your problem what you can do is, go to global variable and replace the old table ID with the new ID.

  • Suggested answer
    keoma Profile Picture
    keoma 32,675 on at
    RE: Compile Error 2009 R2 -> 2013 SP1

    hi,

    tables 2000000002 and 2000000003 were eliminated. use tables 2000000120 and 2000000053 instead.

    check the global variables in the report and replace the subtypes with the new table numbers. for tax addon contact the vendor.

  • Verified answer
    Lourens Profile Picture
    Lourens 25 on at
    RE: Compile Error 2009 R2 -> 2013 SP1

    Hi Raphi,

    Those tables were dropped in 2013 as you can see from the link below.

    msdn.microsoft.com/.../hh997053(v=nav.70).aspx

     

    This leaves you with the 2 options you described.

    Either you leave them there in an uncompiled state so if in future they are required you can modify them to restore their functionality. Eventually they could be deleted once it is clear they are no longer required.

    Or you delete them, but make sure you keep a backup of them before you delete so they can be restored if required.

    Without knowing the content of these reports it is impossible to suggest how to fix them, but it should be possible by using alternative tables.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans