From the Microsoft Dynamics NAV Blogs: Object version tags; Detecting object type; Discontinued component in NAV 2013; Why work with NAV?

A selection of the latest insight from the Dynamics NAV blogs:

• Black Dog Serenade: The Importance of Version Tags in Dynamics NAV Objects;
• Detecting Current Object Type and ID Using Some Funky .NET Interop;
• Discontinued Component NAV 2013 & Later - INPUT BOX (The Input Method is Obsolete):
• Why Am I Doing Dynamics NAV?

Black Dog Serenade: The Importance of Version Tags in Dynamics NAV Objects

On the ArcherPoint blog, Tom Hunt notes that every object in Microsoft Dynamics NAV has a version tag. You've probably seen them in the Object Designer; they look kind of like this: NAVW17.00.00.35026,NAVNA7.00.00.35026,JM7.0.18,SE0.55.12,AP7.00.006

"That one comes from the Sales Header table for a customer running NAV 2013 who has several add-ons and customizations installed. It's awfully long, isn't it? I'll try to break it down and explain what these all mean.

"You'll notice that there are several commas in there. The general rule of NAV development is that every group of people that touches an object leaves its own stamp on it in the version tag, and the tags are separated by commas."

You can see the explanation of what the object tags mean and how they're used so you can understand what's been done to an object here.

Detecting Current Object Type and ID Using Some Funky .NET Interop

On his blog, Vjekoslav Babić asks: Did you ever need to identify ...