Querying Currency Fields in Multi-Currency Orgs

The following syntax is for using convertCurrency() with the SELECT clause:

1convertCurrency(field)

For example:

1SELECT Id, convertCurrency(AnnualRevenue)
2FROM Account

To format currencies according to the user’s locale, use FORMAT() with SELECT() statements. In this example, convertedCurrency is an alias for the returned amount, which is formatted appropriately in the user interface.

1SELECT Amount, FORMAT(amount) Amt, convertCurrency(amount) convertedAmount,
2FORMAT(convertCurrency(amount)) convertedCurrency FROM Opportunity where id = '006R00000024gDtIAI'

If an org has enabled advanced currency management, dated exchange rates are used when converting currency fields on opportunities, opportunity line items, and opportunity history. With advanced currency management, convertCurrency uses the conversion rate that corresponds to a given field (for example, CloseDate on opportunities). When advanced currency management isn’t enabled, the most recent conversion date entered is used.

You can’t use the convertCurrency() function in a WHERE clause. If you do, an error is returned. Use the following syntax to convert a numeric value to the user’s currency from any active currency in your org.

1WHERE Object_name Operator ISO_CODEvalue

1SELECT Id, Name
2FROM Opportunity
3WHERE Amount > USD5000

In this example, opportunity records are returned if the record’s currency Amount value is greater than the equivalent of USD5000. For example, an opportunity with an amount of USD5001 is returned, but not JPY7000.

Use an ISO code that your org has enabled and made active. If you don’t put in an ISO code, the numeric value is used instead of comparative amounts. Using the previous example, opportunity records with JPY5001, EUR5001, and USD5001 would be returned. If you use IN in a WHERE clause, you can’t mix ISO code and non-ISO code values.

You can’t convert the result of an aggregate function into the user’s currency by calling the convertCurrency() function. If a query includes a GROUP BY or HAVING clause, currency data returned by using an aggregate function, such as SUM() or MAX(), is in the org’s default currency.

For example:

1SELECT Name, MAX(Amount)
2FROM Opportunity
3GROUP BY Name
4HAVING MAX(Amount) > 10000

You can’t use ISO_CODEvalue to represent a value in a particular currency, such as USD, when you use an aggregate function. For example, the following query doesn’t work.

1SELECT Name, MAX(Amount)
2FROM Opportunity
3GROUP BY Name
4HAVING MAX(Amount) > USD10000

You can’t use convertCurrency() with ORDER BY. Ordering is always based on the converted currency value, just like in reports.