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

by Linda Rosencrance
published September 14, 2014

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

...

Requires FREE Membership to View

Login
Become a Member Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Linda Rosencrance

Linda Rosencrance is a freelance writer/editor in the Boston area. Rosencrance has over 25 years experience as an reporter/investigative reporter, writing for many newspapers in the metropolitan Boston area. Rosencrance has been writing about information technology for the past 16 years.

She has covered a variety of IT subjects, including Microsoft Dynamics, mobile security issues such as data loss prevention, network management, secure mobile app development, privacy, cloud computing, BI, big data, analytics, HR, CRM, ERP, and enterprise IT.

Rosencrance is the author of six true crime books for Kensington Publishing Corp.

Read full bio...