Thomas Kluson - 2 years ago
Hello Rod, thank you for this. I have tested step 1 to 3 from your instructions, and it worked. I am wondering why Salesforce allows us to access "DefaultCurrencyIsoCode" within a process, but not within a formula. Strange ...
Regarding step 4: I assume this formula field should be created in the object, where currency amounts need to be converted, e.g. in object "Account"? Right? In the formula you use "Owner.Currency__c". Shouldn't we rather use "$User.Currency__c" instead?
Ownly Conseil - 2 years ago
I've created a workaround that might not be a one-size-fit-all solution but it has worked for one of our clients.
1. Create a custom field on the user object called "Currency__c"
Setup>User>Fields and relationship> New> text field >save.
2. Create a process builder that will populate the recenlty created "Currency__c" field with the Currency ISO code.
3. Update all users (this will trigger the above mentioned process builder)
4. Create a custom formula field of the type "number" (not currency) with the next formula:
if( TEXT(CurrencyIsoCode) = Owner.Currency__c , Amount , Amount *(CURRENCYRATE(Owner.Currency__c)))
Then Update your report and dashboards by including that field.
I hope this helps someone
Jason Cardinal - 2 years ago
This would be a huge win for multi-currency orgs. Building reports and dashboards becomes a nightmare the way its currently set up because of the clutter it creates. Being limited on the number of dynamic dashboards you can create (which I'm sure this feature will tie into that limit somehow) it is extremely difficult to truly be efficient without this feature.
Thomas Kluson - 3 years ago
I think this one should be merged too:
Kate Lloyd - 3 years ago
Another 11 year old idea. SFDC, please will you look at the ideas? There are MANY ancient ones which we are desperate for - real holes in the functionality which would make SFDC an AMAZING platform if you would just crack on and fix them. PLEASE. 11 years is a long time in software development!