Considerations for Using Multiple Currencies in Data Cloud

Keep these considerations in mind when using multiple currencies in Data Cloud.

• Data Cloud supports only static conversion rates and ignores dated conversion rates that are enabled in your Salesforce CRM org.
• If a currency’s conversion rate isn’t specified in your Salesforce org, Data Cloud returns a null value for the currency field. To avoid this issue, add currency conversion rates in your Salesforce org or use your own conversion rate DMO.

  You can test the conversion rate using the Data Cloud Query Service conversion function in the Query Editor.

  select Order_ID__c, Sales__c, try_convert_currency(Sales__c, 'USD', 'EUR') as Sales_EUR, Profit__c, cdp_sys_record_currency__c from orders_same_currency__dll limit 10

• If you connect multiple CRM orgs to Data Cloud, use the same list of currencies and conversion rates in each org.
• Data Cloud doesn’t support currency conversions across different CRM orgs connected to it. For example, assume that Data Cloud syncs conversion rates for US dollars (USD) and euros (EUR) from CRM org 1, and Japanese yen (JPY) and Indian rupee (INR) from CRM org 2. In this scenario, Data Cloud doesn’t support these conversions: USD to JPY, USD to INR, EUR to JPY, and EUR to INR. To avoid null values in your conversions, add USD and EUR currency rates to org 2, and JPY and INR currency rates to org 1.
• A currency field in a DMO can support different currencies. For example, the Amount field in a Sales Order DMO can be in USD for one order and in EUR for another. To help with currency conversions in such instances, the cdp_sys_record_currency field, which contains the ISO currency code value, is included by default.
• You can’t use a single-currency org in a sandbox org.

Keep these additional considerations in mind when using multiple currencies in calculated insights.

• All currency fields in a calculated insight must be in the same currency. For example, if a calculated insight includes two measures with currency values, all fields for both measures must be in the same currency.
• When using a calculated insight to aggregate currency values, the currency values must be converted into a single currency.
• When using the builder to create a calculated insight, the builder automatically manages the conversion logic. But, the user must select the currency for the insight output.
• When creating a calculated insight with currency fields using SQL, to adhere to syntax standards, include the try_convert_currency function using this syntax:

  try_convert_currency(Source Currency Field, Source Currency ISO, Target Currency ISO)

• When using the builder to create a calculated insight that includes the currency data type, the builder automatically adds the currency_type_c field. When creating a calculated insight with currency fields using SQL, the user must add this field manually.