Introducing…. Metadata version in NAV 2009 SP1/R2 hotfixes

As a follow up to my previous post, we are happy to announce that, from build 32942, the hotfix releases will detect if objects need to be recompiled and prompt you to recompile accordingly. This will happen when importing incompatible fobs files or when applying new platform hotfixes.

If you try to import fob files from previous (or possibly also newer versions), or if you export them from newer builds (32942 and newer) and back to NAV 2009 R2 or newer versions (up to build 32942), the system will detect that the metadata is incompatible and force a recompilation when imported. The same detection will happen if you apply a hotfix to your system, and your objects need to be recompiled.

In the future, the metadata version (which is now in the Object Metadata table in field 27) will be updated if a compilation will be needed after applying a hotfix, not making it necessary always to re-compile the objects every time you apply a new hotfix (and preventing the RTC client from losing the connection to the server). The current metadata version is 60300, whereas the R2 runtime metadata version is 60200.

Since we are changing a system table (table 2000000071), we need to do a database conversion. Moreover, since the objects are not recompiled with a database upgrade, you also need to recompile the objects that you need. The nice feature now, is that the RTC will prompt you on demand to recompile the objects that need recompilation (basically, the ones you use).

Comments (10)

  1. Natalie K. says:

    Good to hear :-)

  2. Mike G says:

    Finally!!! Thank you!!!

  3. Joerg R. says:


    is this new buildversion already available?

  4. Erik says:

    Please provide a link to the hotfix?

  5. jtorres says:

    Build 32942 should be already available under KB2643210.

  6. Marc says:

    I do not see this build and the I searched the Knowledge base and do not see the one you listed either.

  7. Dave M says:

    Look for the build number.

    The search in the partnersource/customersource web site is pretty useless.

  8. spriess says:

    Build 32942 can be downloaded from KB 2611566 – The RoleTailored client (RTC) becomes disconnected when the Microsoft Dynamics NAV server checks if an object is compiled in the correct version in Microsoft Dynamics NAV 2009.

    KB 2611566 can be found at the following links:

    Microsoft Support:…/2611566


    For a complete list of platform hotfixes released for Microsoft Dynamics NAV 2009 SP1/R2, see:


    Platform Hotfixes for Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2…/nav2009sp1platformhotfixoverview.htm


    Platform Hotfixes for Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2…/NAV2009SP1PlatformHotfixOverview.htm

  9. dimartinez says:


    I have Nav 2009 SP1 (build 29626). I have installed the "Combined Hotfix Release for Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2".

    After that, I open the database and compile all objects.

    Once it is finish, I load the build 32942 (copy the files in the folders as instructions say)

    Then, when I try to open de database, Navision prompts that the database must be converted. I accept but it stops saying that "Field 27 is not defined in the Object Metadata table" and stop the process

    How could i solve it??

    Thank you very much


  10. dimartinez says:

    Solved. The problem was I had not-compiled objects.