Length of field City - Text30 is to short about alappextensions

[Gallimathias]

To cover all city names of the world, the field should be 170 characters long. Or what do I do for example with the Thai city: Krung Thep Mahanakhon Amon Rattanakosin Mahinthara Ayuthaya Mahadilok Phop Noppharat Ratchathani Burirom Udomratchaniwet Mahasathan Amon Piman Awatan Sathit Sakkathattiya Witsanukam Prasit (168 chars, longest city name in the world)

[yrest]

@Gallimathias you could abbreviate it KTMARMAMPNRBUMAPASSWP

[RafaelKoch]

We deploy in Germany too and usually our customers can live with some abbreviations.

If we start this here, what is to stop a discussion about names, street names, item descriptions, resource names.... whatever. I think we need to consider benefit and cost: The benefit is a given but maybe small, the cost is 20 additional charcters extend a plethora of hot tables and/or pretty large tables in the product. In this example Contact->Needs to align with Customer, Vendor, Bank Account. So all Sales and Purchase Docs too, all Posted ones, ... this multiplies quite impressively.
I vote nay :-)

[Gallimathias]

In the western world, we also simply say Bangkok @yrest :D

In general, I would be in favour of lifting the signs restriction. The restriction is rather ridiculous. The SQL Server have a limit of 2 GB text, 250 characters are a joke.

I vote for yes.

[ikoletic]

We do not have plans to extend City text. If you feel strongly about this please make sure to add this as product suggestion on https://aka.ms/bcideas