Description in table 204 "Unit of Measure" about alappextensions

[FilipCrombez]

Hi Stephane thanks for the info but I know already long time the customization possibilities and work arrounds :-) I just want to minimize customization on the standard product.
So I'm suggesting an improvement towards Microsoft for the new Business Central version for being consistent.
Descriptions fields are everywhere at least 30 characters.
So please make this also standard for these 2 remaining description fields in the product.
I just want to hear from the Microsoft team if this will be rejected or be a future enhancement.
Thanks.

[Stephane69006]

No reason. But don't change the value.
If you want a description. I think you should create a new field 50000 description 2.
Because if you change the value. In a nother table in relation you have the same size 10 and maybe you have to change a lot of table in relation with this table/field.

[FilipCrombez]

If there is no reason , I would love that Microsoft expand this description to 30 or 50 like all other description fields (Item.Description, ....)
It is weird and inefficient to foresee a customized field Description 2 for solving this issue. (Also translation table)

[Stephane69006]

Hello Filip,

It's Not Weird, but you need to understand that for each company the rules will be different.
For you, the field Description is small, for my country it's enough, we need only the Code or the international code.
The method in Navision:
You have standard Objects 1, 2, 3
You have Local Objects 10000 for example
You have Objects customized 50000.
If you want something create it,

And in your page, you can create a new var (concatenation) "Description"+" "+"Description 2"

[fvet]

Any update from MS on the status of this issue?

Others interested, please upvote on Experience.
https://experience.dynamics.com/ideas/idea/?ideaid=84a24c76-3bb3-e811-a8eb-0003ff68c780

[ikoletic]

Will ship in April 19 - already in docker images.