Hi @Jason_Tamulonis and @Ayuba_Audu,
Still very much loving this update, but wanted to report a small issue: When you add a pack sync table to the doc, any Date/Time columns from the sync table do not respect the doc’s date and time format options, and just default the American format.
Hello Jason !
So, what did you decide ?
Can we count on international number formatting in 2025 ? 
Yes, I’m working on making it happen.
Thanks for flagging Nad, I am aware of this issue, unfortunately there is a dependency in how documents interfaces with packs and we needed a migration to fix it. We have a fix for this, but it’s blocked on finishing the migration which is taking some time. It is coming though.
Hello @Jason_Tamulonis,
As I am recording a Coda course, I recently had to handle a csv import with numbers, and remembered that for “non american people”, we have to change the locale of our document-to-export before exporting its data to csv (so that numbers can be imported).
Question : Will the international format work with csv import also ? (No more need to import number in american standard 
)
Thank you 
Great question, @Maxence_Walbrou.
The short answer is yes. The general pattern we try to follow for all value-type conversions is to handle them in a central piece of code shared between UX, formulas, API, and automations. Hence, we get consistent behavior across all of them. Most conversions also have two modes depending on the usage: strict and loose. In strict mode, we have an expected format that must be adhered to, but in many places, we use a loose mode that is more user-friendly. Loose mode often has a preferential order that can depend on various factors like column settings, the document’s regional settings, and, eventually, a user’s regional settings.
The fact that we centralize the handling across all of our systems is one of the reasons deploying these changes can take some time.
Thank you @Jason_Tamulonis !
Can’t wait to have this feature 
Do you know when it could be live ?