Creating a multi-option string dimension that can link to custom calculation

We are using Quicksight to embed dashboards for our clients. We have a number of different countries with different currencies and we want to give the clients the option of picking the currency which would then convert the entire dashboard to their chosen currency.

I have tried creating a parameter with multiple string static default value using the needed currencies. I then tried to link this into a calculated field using and we thrown an error message stating you can’t link numeric values to string parameters.

I’m more familiar with Looker as our business visualisation tool and this is the approach I would take if tackling this issue in LookML so I’m hoping to create something similar for a currency dropdown with some help from you.
eg:

 parameter: report_currency {
  type: string
  group_label: "Currency Displayed Filter"
  description: "To be filtered on.  Currency to view, ie. EUR, GBP, USD"
  allowed_value: { value: "EUR" }
  allowed_value: { value: "GBP" }
  allowed_value: { value: "USD" }
  }

I would then link the drop down^ to a calculated field with an additional dimension:

dimension: selected_report_currency {
    label_from_parameter: report_currency
    sql: {% parameter report_currency %} ;;
    description: "To be referenced in Custom Filter.  Filter selection of report_currency; EUR, GBP, USD."
    hidden: no
  }

The output would then be calculated based on something like:
ifelse (${CurrencyString} = 'EUR', {RevenueValue} * 1.17

Thanks in advance!

Related questions that haven’t helped:

Any solution for multi-currency reporting?

Displaying multiple number formats using a single measure

Hi @datagirl!

Should be possible. below please find a simple example in Arena.

Currencies

There might of been something incorrect in your parameter/control setups.

Thank you for being a member of the QuickSight community!!
Ramon Lopez

2 Likes

Thank you Ramon! It looks like the parameter wasn’t working with the multiple string option configured as it needed to be added at control level as a dropdown but all good now!