> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/crms/salesforce/salesforce-currency.md).

# Salesforce Currency

If you have convertCurrency function enabled in your Salesforce organization, HockeyStack by default generates two fields for a single currency field from Salesforce, the field with its original name, and another with the keyword 'static'. The field with the original name pulls the amount value directly from Salesforce. The 'static' field uses the convertCurrency function during ingestion, converting the amount value to your default currency set in your Salesforce account.

In your reports, the non-'static' currency fields will always be converted to the current dollar rate, while 'static' currency fields will remain as the resulting value from convertCurrency.

### Example:

Let's say your default currency in your Salesforce organization is USD, and you have a field named `deal_arr__custom` with the value of 100 GBP. When HockeyStack pulls this data from Salesforce, it generates two fields - `deal_arr__custom`  and `deal_arr_static__custom` . Inside the HockeyStack database, the resulting values of the two fields will look something like the following.

* `{ deal_arr__custom : 100, currency: GBP }`
* `{ deal_arr_static__custom: <SFDC converted amount from convertCurrency(deal_arr__custom)>, currency: USD }`

When you create a report using these 2 fields, HockeyStack will convert `deal_arr__custom`  to USD with the most current exchange rate, and `deal_arr_static__custom` will not be affected by the current exchange rate, but pull value directly from our database.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hockeystack.com/integrations/crms/salesforce/salesforce-currency.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.