NAV2016CU2 | Symbol Menu & More


NAV 2016 Cumulative Update 2 is released. I have to admit, normally I don’t pay that much attention to updates, but the last ones are on my radar because of some promisses.

Symbol Menu

Nobody could be happier with the new code editor than me. It makes me more productive and makes our environment sexier and more attractive to young people.

However, the very first piece of feedback I gave was that in some cases the Symbol Menu was not bad.

NAV2016SymbolMenu

This feedback was first ignored during the Technical Preview process, but due to pressure after release it is now back.

Glad I was not the only one.

Events & Extensions

There are a couple of interesting KB articles in CU2. Mainly about Extensions and Events.

376710 You cannot publish an extension if it contains too many objects.

So somebody is trying to wrap their entire vertical solution in an Extension? 😉

376969 An extension object cannot be added when a deleted base object had the same ID.

This is a strange one. First and foremost, if you package an extension ALWAYS use ID’s in you CfMD range. I don’t recommend packaging custom objects as Extension.

You can change the automatically generated ID in the Database-Alter menu on the Advanced Tab.

StartID UidOffset

I admit, it does not work too well with distributed development where each developer has their own database.

Hopefully in the (near) future Microsoft will make the required changes in NAV to make proffesional development easier out of the books so we can safely say distributed development is easy. I would also like to see GIT support.

Advertisements
This entry was posted in Dynamics NAV, General, Product News. Bookmark the permalink.

7 Responses to NAV2016CU2 | Symbol Menu & More

  1. waldo1001 says:

    Long live centralized development! 🙂

    No, really, when distributed development, you should “control” your environment (like Kamil does). So “automagically” set up db’s and stuff. One step is updating this setting .. and when it’s managed, it’s set as well.
    No need to say that PowerShell is the way to manage it 😉

    Liked by 1 person

    • Mark Brummel says:

      I partly agree. It is still hard to decide which developer gets which ID. How many “gaps” do you leave? I would like Microsoft to move to a more modern way of handling that. This should have been done before they introduced Extensions.

      Like

      • What we do for now in our small (4) team is that each developer has a custom sql script that he runs on every restored DB, which inserts his user into the DB and also updates uidoffset with his custom number. The problem I have personally is sometimes I forget to set a custom uid whenever I create a ‘branch’ database to work on some complex feature, then I have issues during my own merge 🙂

        Liked by 1 person

      • Mark Brummel says:

        Yup. And good old PowerShell does not give a heads up. You need MergeTool for that.

        Like

  2. Pingback: NAV2016CU2 | Symbol Menu & More - Mark Brummel - Author of Microsoft Dynamics NAV 2013 Application Design

  3. waldo1001 says:

    You can program the check into PowerShell, just like Per did in Mergetool :p.
    And on top of that: you can provide a complete branching-script in PowerShell easily – try that in Mergetool! :p

    Like

  4. Pingback: NAV2016CU2 | Symbol Menu & More | Pardaan.com

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s