This Product Ideas board is currently undergoing updates, but please continue to submit your ideas.
Hi everyone, the title basically sais it all :grinning_face_with_big_eyes:
absolutely this one as well as choosing whether the currency symbol is before or after the amount. it is disappointing how often simple features take way too long to appear for international users.
partly related to the 2nd pont by @Parashar_Shah (unless im doing something wrong) when I use the formula to display dates in the 3 letter month format and sort it in a view it does so alphabetically which it obviously shouldnt or am I doing something wrong?
I just imported a CSV into a new base.
I’m in England, so the system that generates my reports automatically uses the DD/MM/YYYY HH:MM format for dates.
When I imported the data, everything looked fine. At the time it was a text field.
I decided to change the field type to Date. Before any of the data was converted, I made sure to choose ‘European’ in the dropdown.
The problem is that upon clicking ‘Okay’, Airtable does not associate the choice of date format with the pre-existing data in the fields.
So what happens is that any dates before the 12th of a month are reversed (for example the 9th of December becomes the 12th of September), and any dates that occur after the 12th of the month are simply wiped as they’re not recognised as a date.
This leads to a table that looks more like this:
Is it possible for the Date field to take the date format choice into account before it decides how to parse this data?
Hi Matt. A quick thought… Maybe you could format your source file date field in the American way, export to your Csv, import to airtable. Airtable should treat your field as a date and not a text so you finally can change it to European format.
Hi Emilio, good idea. I’ll try it.
Definitely think this is a bug worth fixing, though.
The custom currency symbol is awesome, it suits the needs of my team perfectly…well almost, the ability to select which end the symbol appears would take things to the perfect level.
After months since first requests for support of a decimal comma (3,14 instead of 3.14) have appeared here nothing has changed in Airtable. That’s a pity. Instead we’ve got a new field type and a new design.
A new field type is nice - but it does not make Airtable more usable to many, many potential users in Europe. I won’t be able to entice anyone of my customers to use Airtable as long as their clerks and office workers cannot use their native number format. Even simple applications cannot be moved from Excel to Airtable without regional input and output formats. I cannot imagine how much revenue will not be generated due to this lack of basic international functionality. It’s so basic, even, that the iPad/iPhone versions of Airtable have it - but the online and desktop versions are lacking it (at least for the decimal comma).
Please, Airtable team, provide all the basic formatting options relevant in most parts of the world outside the US. You’ve created a great tool - but all its cool features are facing a basic constraint: internationalization. It’s not just techies and nerds and geeks using your product. Or at least it shouldn’t
I have excactly the same problem when importing cvs with local date format (Switzerland).
I have already notified the Airtable team on this behavior.
Hope it will be corrected soon
It would be lovely to have a localization option for the menu language.
At least a language-settings file for menu conversion and making it open-source would work. Also community can create lot of language files without any development cost for airtable dev. team.(like wordpress).
I would like to support to translate to German.
So when is more international formatting support coming to Airtable (especially the decimal comma)?
The lack of it is holding me back to wholeheartedly recommend Airtable to my clients.