NAV2013R2: Extended Version List

This is something many partners have been wanting for a long time. With NAV2013R2, it’s finally happening: Finally it’s possible to put more then 80 characters in the Version List column in the Object Designer. The field has been extended to 248 characters, as you can see below:

The Object Table in NAV2013

The Object Table in NAV2013R2:

Finally.. 🙂

5.00 avg. rating (98% score) - 4 votes

Permanent link to this article:


2 pings

Skip to comment form

  1. now if they’d only improve the import worksheet.. 🙂

  2. What do you mean exactly?

    • Vincent Vancalbergh on September 12, 2013 at 8:36 pm
    • Reply

    Oh my gawd !

    And about the Import Worksheet, I think he means the text-boxes in the bottom that are currently already too short 🙂

  3. Great.

  4. Cool.. thanks for sharing Waldo…

    About the import worksheet – I second that.
    Would be great to have some code-merging features (like in Dynamics AX) during import.
    So for example there is a confilct, you could choose to view code side-by-side and “flip over” code to the existing object, without importing the new object. I know this is easier in AX because of the layered application objects, but stilll… could be great 🙂
    I’m not sure how to visualize this though, with triggers, sections etc..

    Thanks again for sharing!

  5. Thanks for the suggestions! You’re totally right.
    We’re so used to doing it a little bit sloppy, that the obvious efficient ways are sometimes slipping our minds 🙂

  6. That’s a great idea Søren!

  7. Actually.. the whole idea of the layered objects in AX is pretty neat.
    Imagine having access to the standard codeunit 80 inside NAV, alongside with the partner-modified version, and the customer-modified version too. And when importing a new object (or when designing the codeunit) we could “show layered versions” of the object, and push around code to the “real” object layer.

    So, something like always keeping track of objects and saving these in some tables. Hmmm.. wasn’t someone developing an addon to handle this, by the way? (anyway, would be great to have “a way back to the core NAV”, or at least to see what the objects looked like earlier.

  8. Now that’s good news. As for the layered appoach: Yes that would be neat. Basically we’re doing nothing else with mercurial/git during development. A merge worksheet like in tortoisehg (using tortoisediff for the merge) would be cool. When you think this to the end, you would have a source repository in git, could rebase and recompile all in NAV. And the patches from Microsoft would be changesets… cool.

    • Peter on September 13, 2013 at 12:42 pm
    • Reply

    Don’t hold your breath regarding expanding the version list in the bottom. I requested that more than 3 years ago: 🙁

    • Jan Pieter on September 13, 2013 at 12:53 pm
    • Reply

    Think I will be happy all weekend about this news! 🙂

  9. Glad that I could be part of that 😉

  10. 🙂 for the improvement to the import worksheet I mean – smarted version matching and filtering, ability to save individual files from import worksheet to TXT, ability to compare contents..

  1. […] Continue reading » […]

  2. […] Bron : Waldo’s blog Lees meer… […]

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.