I believe all community would clearly benefit with this suggestion, mainly because we have reached a point of no return concerning developing extensions in AL.
Comments
over 5 years?!
Category: Development
Even with the introduction of namespaces, the limit of 30 characters leads to unreadable names of tables and fields! Please increase!
Category: Development
This is badly recommended now, as the same name is not allowed in multiple apps. At least, I would say 50 character is must.
Category: Development
It is now 3 years after this idea was suggested. What is the status of this Microsoft?
Category: Development
I'm with @David on this one.
In order to have readable code, variables (Including Table Names) needs to be readable.
CustSalsPersnCredLimntSLSPTE is not readable ...
Category: Development
SQL standard is 128 Characters, so we should be the same in AL. It is time for all the old Navision Native database limitations to be dropped and instead that we consider BC to be a part of Microsoft and follow the Microsoft way of doing things.
Thus I would prefer to see the length increased to 128.
Category: Development
And change prefixes to namespacing, we don't live in the stone age.
Category: Development
This is definitely required, but to repeat some of the comments above - why 50 characters, make it a 100 or simply unlimited.
Category: Development
Well, yes. Enums are limited to 120 characters in name if I remember correctly. I like to see the same length for other object types. But there is an issue which Peter raised somewhere on Yammer.
Category: Development
This is badly needed. Having just upgraded a large c/al project to al I am having to shorten names to accommodate the prefix. As we now need to reference objects by name I am constantly having to look up what the name was abbreviated to rather than just type what the name should be.
Category: Development
Business Central Team (administrator)
Thank you for your feedback. We are considering adding it to our longer term roadmap.