Bug: Currency fields exported to Excel as text with U+202F thousands separator

Please confirm that the bug report does not already exist

• I confirm there is no existing issue for this bug.

Steps to reproduce

Steps to reproduce

1. Create a Currency field with the following settings:
   • Currency Locale: French (fr-sn)
   • Currency Code: EUR
   • Precision: 1.00
2. Enter a value ≥ 1000 (e.g. 3116).
3. Download the view as Excel (.xlsx).
4. Open the file in Microsoft Excel.

Actual behavior

• The value is exported as a formatted text string ("3 116,00 €") instead of a numeric value.
• The thousands separator is U+202F (NARROW NO-BREAK SPACE), which is what Intl.NumberFormat('fr-sn') produces. Excel's formula bar does not render it properly and shows an unknown glyph: 3□116,00 €.
• =UNICODE(MID(F2,2,1)) returns 8239 (U+202F), confirming the character.
• Since the cells are text, they cannot be used in formulas (SUM, etc.), numeric sorting or pivot tables without manual cleanup.

Desired Behavior

Currency values should be exported as numeric cells (e.g. 3116) with an Excel number format matching the field configuration (e.g. #,##0.00 [$€-fr-sn] or #,##0.00 "€"). Excel then displays the value according to the user's regional settings, and the data stays usable for calculations.

At a minimum, if exporting as text is intentional, U+202F should be replaced by a regular space (U+0020) or a no-break space (U+00A0) for better compatibility.

Project Details

• NocoDB version: <version>
• Deployment: <Docker / self-hosted / NocoDB Cloud>
• Database: PostgreSQL
• Excel version: Microsoft 365

Attachments

No response