The FX Currency Selector lets you switch the currency displayed in your dashboards, Excel files or other components at the click of a button — without duplicating widgets or rebuilding your data. Once your tables are configured with Monetary fields, every eligible widget can toggle between your original posting currency and any of your reporting currencies (for example, USD, EUR, or GBP).

Note: This feature is being rolled out gradually. If you don't see the FX selector in your environment, contact your Customer Success Manager to have it enabled for your organization.

How It Works

Datarails distinguishes between two kinds of monetary amounts in your tables:

• Posting Amount — the original transaction amount, in its local (posting) currency. This is the source amount as recorded in your ERP or source system.
• Reporting Amounts — converted amounts, each mapped to a specific reporting currency (e.g., Reporting Amount USD, Reporting Amount EUR). These are typically populated by your FX rate lookups or calculations.

These fields are marked in your tables using the Monetary field designation. On top of them, every table that contains Monetary fields automatically exposes a Reporting Amount field — a system-created, currency-aware placeholder. When you build a widget or a dr.get function on Reporting Amount, Datarails resolves its value at runtime according to the currency selected in the FX selector: the posting amount field when None is selected, or the matching reporting amount field when a currency is selected.

Important: only widgets built on Reporting Amount respond to the currency selector. Widgets that use a concrete field directly — the posting amount field or a specific reporting currency field — always show that field's values, regardless of the selected currency.

Prerequisites

• FX feature enabled — The FX Currency Selector must be enabled for your organization.
• Monetary fields configured — An admin must tag the relevant fields in your tables (posting amount and one field per reporting currency). See Step 1 below.
• Reporting amount data — The reporting amount fields must contain converted values, for example via your existing FX rates lookup.
• Dashboard permissions — Any user who can view a dashboard can use the currency selector; configuring Monetary fields requires table editing permissions.

Step 1: Define Monetary Fields in Your Tables (Admin)

Before the selector can do anything, Datarails needs to know which fields in your tables are currency-aware.

1. Go to the Tables section and open the relevant table (for example, Financials).
2. Open the field settings for the field that holds your original transaction amounts.
3. In the FX Settings section, set the Currency type to Posting. This field becomes the table's canonical Posting Amount.
4. Next, for each reporting currency you want to support, open the field that holds the converted amounts and set:
   • Currency type — Reporting
   • Currency code — the 3-letter ISO code (e.g., USD, EUR, GBP). Please note: You can add a custom currency code. This can help you differentiate between two scenarios of the FX rate or keep a budgeted fx rate for future BvA comparisons.  
   • Symbol (optional) — a display symbol such as $ or €

5. Save. Fields tagged this way display a Monetary badge next to their type in the Table Fields screen, and the posting currency field is flagged so you can see at a glance which field is the table's posting currency.
    

   

Validation rules to keep in mind:

• Each table can have only one field marked as the Posting Amount.
• Each reporting currency can be mapped to only one field per table. If you try to add a duplicate, you'll see: "There is already a reporting amount with this currency code."
• A currency code is required for every reporting amount field.
• A monetary field (either posting or reporting) amount field must be numeric.

The Reporting Amount Field

As soon as a table contains at least one Monetary field, Datarails automatically adds a Reporting Amount field to it. This is the field to use whenever you want a widget, dr.get formula, or Datarails Excel Table to follow the currency selector. A few things to know about it:

• Logical field — it does not store data of its own. It resolves to one of the table's Monetary fields based on the currency selected at runtime.
• Protected — it cannot be deleted or renamed, and its data type is fixed to Monetary. Its format and category can still be edited.
• Sum only — the only aggregation function available for Reporting Amount is Sum; other functions are disabled.
• Where it appears — in the widget editor's Value section, the dr.get editor, and the Datarails Excel Table editor. It is only shown for tables that have Monetary fields. 

Step 2: Switch Currencies in the Dashboard

1. Open any dashboard.
2. In the dashboard header bar, find the FX dropdown (located between the Filters and the date picker).
3. Click the dropdown. You'll see:
   • None — widgets show original posting amounts.
   • One entry per configured reporting currency, shown with its symbol (e.g., USD - $, EUR - €). Your organization's default currency always appears first in the list.
4. Select a currency. All currency-aware widgets (those built on Reporting Amount) immediately switch to display values from the matching reporting amount field.
5. To return to original amounts, select None.

The selector opens with your previously saved selection for that dashboard; if you haven't made one yet, it opens with your organization's default currency (see below).

Which Widgets Are Affected

How calculated KPIs behave: conversion happens before calculation. For example, if a widget shows Gross Margin = (Revenue - COGS) / Revenue and you select USD, Revenue and COGS are each resolved in USD first, and only then is the margin computed. This keeps ratios and KPIs consistent across currencies.

Tip: if you want a widget to always show one specific currency — for example, a "Revenue (USD)" KPI that should never change — build it on the concrete field (e.g., Reporting Amount USD) instead of Reporting Amount. The currency selector will leave it untouched.

Step 3: Use the Selector in the Widget Editor

The same FX selector is available in the Widget Editor header, so you can preview a widget in any currency while building it.

1. Open a widget for editing. The currency you selected on the dashboard carries over — it is not reset.
2. To make the widget currency-aware, add the Reporting Amount field to its Value section. Only the Sum function is available for this field; other functions are disabled.
3. Use the FX selector in the editor header to preview the widget in different currencies. The preview resolves Reporting Amount just like the dashboard view.
4. Build the widget once — there is no need to create duplicate widgets per currency. The selector determines the displayed currency at runtime.

Setting a Default Currency (Super Admin)

Your organization can define a Default Currency so that dashboards, Excel workbooks, and builders open with a consistent currency state.

• Who can change it — Only Super Admins can set the default currency directly from any currency selector in the web app. For all other users, the control is visible but disabled, with the tooltip: "Only a Super Admin can change the default currency."
• Where it applies — The default currency appears first in every currency selector dropdown, and any selector without a previously saved selection opens with the default.
• "None" is allowed — The default can also be set to None (posting currency).
• Saved selections win — Saved views, workbooks, and previously generated files that already store a currency selection keep it. The default only applies where no saved state exists.
• Older Excel add-in versions — If a workbook is opened with an add-in version that does not support currency conversion, dr.get Formulas and Datarails Excel Tables present values in the default currency.

Saved Views and Persistence

The currency selection behaves like a dashboard filter:

• Per-dashboard memory — your last selected currency is remembered per dashboard and restored when you reopen it (it survives a page refresh). If you have never made a selection on a dashboard, it opens with the organization's default currency.
• Saved views — when you save a dashboard view, the FX selection is saved with it. Loading the view restores the currency.
• Multiple views, multiple currencies — different saved views of the same dashboard can each have a different currency (for example, a "Group USD" view and a "Local EUR" view).

Learn more about saved views in Dashboard Customization.

Currency Selector Beyond Dashboards

The same currency selection experience extends to the other Datarails surfaces where you consume monetary data.

Excel Add-In

Workbooks that use Datarails formulas gain a workbook-level currency selector in the add-in, with the same options as the dashboard (None for posting currency, plus your reporting currencies).

• What it affects — dr.get Formulas and Datarails Excel Tables built on the Reporting Amount field resolve to the selected currency. Excel formulas that consume those outputs (e.g., a Gross Margin calculation) inherit the currency automatically, and drilldowns reflect it as well.
• What it doesn't affect — Manual ranges, static values, formulas that don't depend on dr.get, non-monetary measures (counts, quantities), and flat Datarails tables.
• Templates and refreshable reports — Refresh actions re-evaluate all dr.get formulas using the currently selected currency, with no formula changes needed.
• Split files — As with global filters, the currency selection is locked in split files; recipients cannot change it.
• Older add-in versions — If a workbook is opened with an add-in version that does not support currency conversion, values are presented in the organization's default currency.
• Errors — If a requested currency is not supported by the table, dr.get returns a descriptive error (e.g., #UNSUPPORTED_CURRENCY) with a matching warning in the add-in pane — never a silent zero.
   

Report & Budget Builder

A Currency selector is available in the builder toolbar whenever the selected function is based on a field defined as a posting currency. The options are None plus the reporting currencies that exist in the table the builder's function is connected to (for example, the currencies in the Financials table).

• Web presentation only — Changing the currency affects the report presentation in the web. Excel files already generated from the builder are not changed retroactively.
• Calculated rows and columns — Arguments are converted to the selected currency first, and the calculation is evaluated afterwards (e.g., for "row 2 / row 3", both rows are converted before dividing).
• Downloads — When you download a report, the Excel file opens with the same currency selected in the Excel currency selector. If the add-in version doesn't support the currency converter, the file opens in the original currency.
• Split budget builders — When a budget builder is split, the currency selection is preserved and the files are created with the selected currency.
• Publishing from Excel — Updating a budget builder from Excel ("Save and publish to Excel") behaves like global filters: it does not change the Excel currency selector.
   

Troubleshooting

A widget shows "No data available. The selected currency is missing from the table."

Problem: The widget's underlying table does not have a reporting amount field for the currency you selected.

Solution:

• Select a different currency in the FX selector, or select None to show posting amounts.
• To support this currency, ask your admin to add a Monetary reporting field with that currency code to the table (see Step 1) and populate it with converted values.

A widget shows "The posting currency is missing from the table"

Problem: None (posting currency) is selected, but the widget's underlying table does not have a valid Monetary field tagged as the posting amount.

Solution:

• Select a reporting currency in the currency selector, or
• Ask your admin to tag the table's posting amount field as a Monetary field with Currency type = Posting (see Step 1).

The FX selector doesn't appear in my dashboard

Problem: The dropdown is missing from the dashboard header.

Solution:

• The feature may not yet be enabled for your organization — contact your Customer Success Manager.
• Verify that at least one reporting currency has been configured on your tables; the selector's list is built from the currency codes defined across your tables.

A currency I expect is missing from the dropdown

Problem: The FX dropdown doesn't list one of your reporting currencies.

Solution:

• Check that a field with Currency type = Reporting and that currency code exists in the relevant table.

   

Some widgets don't change when I switch currency

Problem: A widget keeps showing the same values regardless of the selected currency.

Solution:

• The selector only affects widgets whose Value section uses the Reporting Amount field. Open the widget in the Widget Editor and replace the concrete amount field in the Value section with Reporting Amount (Sum).
• Widgets built on a concrete Monetary field (e.g., Reporting Amount USD or the posting amount field) are intentionally unaffected — this is how you pin a widget to a fixed currency.
• Counts, quantities, and dimension-only widgets are not currency-aware by design.

I can't change the default currency

Problem: The default currency option is greyed out, with the tooltip "Only a Super Admin can change the default currency."

Solution:

• Only Super Admins can change the organization-level default currency. Ask a Super Admin in your organization to update it.
• You can still change the current currency selection for yourself on any dashboard — the default only controls what selectors open with when no saved selection exists.

Frequently Asked Questions

Does switching currency change my underlying data?
No. The switch is visual only — the selector changes which field the widgets read from. Your data, filters, and widget definitions remain unchanged.

Do I need to rebuild my widgets to use this feature?
You build each widget once, using the Reporting Amount field in its Value section — that single widget then serves every currency. Existing widgets built on a concrete amount field need their Value section switched to Reporting Amount to become currency-aware. This replaces the old approach of building duplicate widgets or dashboards per currency.

Why can I only use Sum with Reporting Amount?
Sum is the only aggregation supported for the Reporting Amount field in this release. Other functions are disabled when Reporting Amount is selected.

Where does the list of currencies come from?
It is the unique list of currency codes defined on Monetary reporting fields across your tables. Adding a new reporting currency to a table adds it to the selector.

How are the converted amounts calculated?
In this release, reporting amount fields hold values you maintain — typically populated through your existing FX rates lookup or calculated columns. The selector reads those fields; it does not calculate rates itself. See Lookups Overview for how FX rate lookups work.

Is my currency selection shared with other users?
Your own last selection is remembered per dashboard for you, and it does not affect other users. What is shared: the organization-level default currency (what selectors open with when no saved selection exists, set by a Super Admin) and any public saved views that include a currency selection.

Is the currency selector available in Excel or the Report Builder?
Yes. The Excel Add-In offers a workbook-level currency selector that drives dr.get formulas and Datarails Excel Tables, and the Report & Budget Builder has a currency selector in its toolbar. See the Currency Selector Beyond Dashboards section above for details. Availability may vary during the gradual rollout.

Updated August 02, 2026 17:26