Lede: Your Deluge script succeeds but the account "Home Currency" or a currency field doesn't change. This usually stems from confusing account-level currency settings with record-level currency fields, or from locale/formatting problems that block Deluge updates.
What it means — concrete explanation tied to the Zoho API surface, cited [^N]
The "Home Currency" is an account-level setting managed under Setup > General > Company Details > Currencies and cannot be freely changed via normal API or Deluge calls once set; changing it requires consent and intervention from Zoho support because it affects all records and exchange-rate configuration [5][6]. Separately, Deluge update calls operate on module records (for example zoho.crm.updateRecord("Deals", id, map)) and require the correct field API name, data types, and record structure; a script that calls updateRecord but uses the wrong key or wrong payload structure can return no visible change even when the function reports success [4][8]. Finally, recent CRM issues around decimal and thousand separators have caused Deluge calculation errors on Currency/Decimal fields for locales using formats like 1.234.567,89; that can make updates silently fail or mis-parse values [1][2].
Common causes
- Attempting to change the account-level home currency from a Deluge script instead of editing company settings or contacting support [5][6].
- Using the wrong API name or payload structure when calling zoho.crm.updateRecord (wrong map keys, nested custom field access), so the record never receives the intended value [4][8].
- Passing numbers with locale-specific separators (commas or dots) that CRM/Deluge mis-parses; CRM does not auto-convert pasted comma decimals the same way Books sometimes does [1][2].
- Missing permission or trying to update a system-protected field that only super admins or support can change [5].
How to fix it
- Confirm what you must change: open Setup > General > Company Details > Currencies and verify whether you need to change the account "Home Currency" or a module-level currency field [5].
- If you need to change Home Currency, do not script it. Have your super admin contact support@zohocrm.com and request the reset; Zoho must perform it and will explain consequences (multiple currencies deletion, symbol changes) [5].
- If you are updating a record field, inspect the record with zoho.crm.getRecordById("Module", id) to get the exact API names and structure before updating; use the returned keys in your update map, e.g., mp.put("FieldAPIName", value) and zoho.crm.updateRecord("Module", id.toLong(), mp) [4][8].
- Normalize numeric input before sending: strip thousands separators and convert comma decimals to period decimals in Deluge (or pass numeric types instead of strings) so CRM parses the value correctly; test with a simple numeric literal first [2][1].
- Add debug logs and check the update response object for errors or error codes; if the response shows a failure or unexpected structure, capture that output and compare to your payload [4][8].
- Retry after applying fixes. If behavior matches a known bug (e.g., specific number format crashes Deluge), check the Zoho community/announcement and apply any provided workaround or patch notes [1].
When to escalate
Escalate to Zoho Support when you must change the account home currency or when you've validated correct field names/payloads but Deluge still fails