Hi everyone! I was hoping to get feedback from people with regards to Currency Fields in Shotgun.
Currently we only support a dollar symbol (or nothing at all) when using currency fields, which has been something of a limitation. I’m keen to find out how people would like for these to be more flexible, specifically in terms of:
Which other currency types are needed?
Is there a need to mix currency types within your individual sites?
…within individual projects?
…within individual fields?
When importing from spreadsheets into a currency field, is it ok to ignore any currency symbols in those files and just look at the number?
Not sure what the right solution is but let me illustrate some of our constraints.
We have multiple projects in multiple regions and each of those projects might use a different currency and have multiple currency fields across multiple tables.
Would be great if we could create a calculation field to present a user the calculation of a base currency (Dollars) translation to a target currency ( Euros) using an exchange rate field from the project entity and or some other linked field. This means supporting deep fields for calculations.
In some instances it would be convenient to be able to describe the currency at the page view or via a calculation field. After all its just a float with a decorator.
Which other currency types are needed?
So many! We use a custom entity to manage a list of project-specific currencies (and their exchange rates), using currency code formatting. This means we typically require two fields to track the Amount (currency field) and Currency (entity field), since we’ve disabled the currency sign display in the site preferences. This is not ideal (relying on two fields), but is functional. Would definitely be interested in seeing improved currency support!
Is there a need to mix currency types within your individual sites?
Yes.
…within individual projects?
Yes.
…within individual fields?
If this is referring to having, for example, an Amount EUR and Amount USD fields on a single entity, then Maybe. We do this to an extent today. Ideally, would be interested in improved currency (and exchange rate) support that could allow you to toggle the currency display based on the project-defined currencies and exchange rates.
When importing from spreadsheets into a currency field, is it ok to ignore any currency symbols in those files and just look at the number?
Today, Yes. But with improved Currency support in Shotgun… Not sure. Would love to see a proposal for where you’re thinking of taking this!
This would be really useful for us, at the moment we have 20 vendors working across multiple territories bidding in £,$ & €. As an aside, our online PO system sets the currency of the vendor, so all transactions with that vendor are in their chosen currency. As we’re tracking bids across different currencies we have to convert the excels before importing into SG
It’s quite amazing that Shotgrid is able to work in 4 different languages but only supports one currency.
I would have thought that implementing user control that allows changing one $ sign with a £ or € sign would be a walk in the park compared to a new language.
Why would something like currency be hardcoded in the first place?!
It’s like hardcoding timecode filed, nobody in their right mind would do that knowing how many timecode standards that are out there.
Please SG Team, do some small updates every now and then to keep the ship moving.
Hello,
I am more than amazed that this conversation has been on for literally years
and you still can’t change the currency filed symbol.
Do you guys at Shotgrid consider that US Dollars is the only currency people use?
More seriously, we are paying for a production tracking tool here.
Can you please advise on how to deal with this?
All I would say is to keep submitting this to the Productboard and perhaps make a ticket also.
Just posting it on the forums won’t make it visible.
However, saying that, you can make your own support for currency’s in ShotGrid by using Custom Entities to track these and their conversions.
It depends on the use case.
Hi folks.
Just a quick update to this thread that users now have the choice of 6 common currency symbols (previously, we only had the dollar sign: $) or the option of a custom option limited to 5 characters (NZD$, USD$, etc).
I hope you’re well. I believe there’s a ticket somewhere that mentions a bug whereby calculated fields defaults the dollards, even if the source amounts are in a different currency. Could this be looked at as I would really like to get some costs out of SG and I can see this causing issues.
Hey @Michael_Illingworth! Thanks for calling that out, and watch this space
When we did this work for more currency support in currency fields, we deliberately excluded working on calculated fields to keep the scope manageable, and to see how the feature landed. We’ve since had enough feedback and usage signals back from customers that is a useful feature, and we’ve continued investment in this space.
And following on from this, we’ve just released currency support in calculated fields.
It works like the currency field: when we detect the TO_CURRENCY calc’ being used, we give you the choice of 6 common currency symbols with an optional custom symbol if you need.
