Skip to content
Vjeko.com
  • AL Object ID Ninja
  • Blog
  • Control Add-ins
  • Tips & Tricks
  • About
Menu Close
  • AL Object ID Ninja
  • Blog
  • Control Add-ins
  • Tips & Tricks
  • About

Description

  1. Home|
  2. Blog|
  3. Description

Length of G/L Account Name in NAV 2013

  • Post published:June 10, 2012
  • Reading time:1 min read

imageA small but important change often slips under the radar of the What’s New kinds of documents. One of those is the standard length of the Name field in G/L Account table. I’ve just noticed that in Microsoft Dynamics NAV 2013 the length of this field has been increased from 30 characters to 50 characters.

While this seams a minor thing, it’s actually a huge improvement. If 30 characters was not enough in previous versions, increasing it was not a simple thing to do, and required you to change thirty or so other objects as well. It was in fact one of those annoying things that you better got used to, rather than changed. Yes, I’ve seen customers who insisted on changing it, but most of them simply gave in.

In NAV 2013, this change is not only about G/L Account – the length of all Name and Description fields in all master tables has been consistently set to 50. In the previous versions of NAV the length varied between 30 and 50, but now all of the master table Name and Description fields are of length 50.

A small step for man, a giant leap for mankind.

Continue ReadingLength of G/L Account Name in NAV 2013

Subscribe to Vjeko.com

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 852 other subscribers

Search Vjeko.com

Recent Comments

What You’re Ac… on Context Engineering – Th…
Antonio del Pozzo's avatarAntonio del Pozzo on I don’t trust my agents…
Vjeko's avatarVjeko on I don’t trust my agents…
Matthias König's avatarMatthias König on I don’t trust my agents…
Vjeko's avatarVjeko on I don’t trust my agents…

Most popular posts

  • I don't trust my agents either
  • What You're Actually Saying When You Say "AI Doesn't Work"
  • OnAfter table event subscriber patterns and antipatterns
  • When GUIDs Collide: The App ID Problem Nobody Expected
  • Context Engineering - The Thing Almost Nobody Is Actually Talking About

Previously on Vjeko.com

  • 2026 (15)     
  • 2025 (7)     
  • 2024 (3)     
  • 2023 (16)     
  • 2022 (2)     
  • 2021 (17)     
  • 2020 (16)     
  • 2019 (26)     
  • 2018 (14)     
  • 2017 (12)     
  • 2016 (23)     
  • 2015 (37)     
  • 2014 (40)     
  • 2013 (9)     
  • 2012 (23)     
  • 2011 (15)     
  • 2010 (55)     
  • 2009 (75)     
  • 2008 (76)     
  • 2007 (8)     
Copyright © 2026 Vjeko.com

By continuing to use this website, you consent to the use of cookies in accordance with our Cookie Policy.

Accept