Roger Farrow - 5 years ago
It does seem odd that this piece of functionality is not standard, and forms a major stumbling block for currency handling. |
Nicola Byers - 5 years ago
We use Salesforce to record all orders. If the exchange rate changes then all orders in the system from all time change to the new rate. This is ridiculous. How can this be? The dated exchange rate needs to apply to all objects currency related. |
Keith McVitty - 5 years ago
Surely this is a piece of basic functionality that should be out of the box as standard. Without it, it means that a lot of our reporting doesn't work on a year to year basis. It's been open for 8 years, so it's not exactly a new requirement! |
Michael Dawson - 5 years ago
This is much needed and should be on the Roadmap. It is all well and good to say their is an app for that, but Salesforce should be listening to their customers. |
Randi Edelman - 5 years ago
Although I have no statistical proof on the ratio of international companies vs. those that are localized in only one country; I can only assume this issue is a common occurance for Salesforce customers and affects all international companies, including my own. From an admin point of view, it is frustrating to have a CRM system that is capable of tracking currency rates, but the advanced settings is only available for one particular object (Opportunities). Our users have ignored the currency conversion rates that are static, as they are completely wrong and it's causing them to not believe in our CRM system. This is hindering our user adoptation (as I now have removed the currency fields due to this) and I am shocked this is not being looked into further by Salesforce, which may I add, is also an international company. Product management & development team: May I request you please reconsider this and kindly add this to your roadmap. |
Sebastiano Bertani - 5 years ago
Without this the multi currency cannot be properly used with custom objects. We have Invoices coming to SForce from a 3rd party system (Zuora) and we cannot aggregate them to match the opportunity amount as the exchange rate applied cannot be related to the date of the invoice itself. |
Patrick Crowley - 5 years ago
I find it interesting that despit the need by any company using multicurrency who wants to use the system as designed are simply told "No, we arn't even thinking about working on that. Go spend more money on the AppExchange." This is basic functionality if you want to report in multicurrecy so not sure why this has been ignored for years. |
Ignacio Jiménez - 6 years ago
Same issue here. What worries me the most is the fact that this feature is not even in a Rodamap. |
Asa Strout - 6 years ago
There is no reason that a feature like this should not be supported natively by Salesforce.com. On custom objects a controlling date field will need to be identified to call out the exchange rate date. This gives the administrator the control set-up the management of the currencies on any of their objects they want to. |
Stefanie S - 6 years ago
You point to apps that are not able to leverage dated exchange rates with the standard currency fields (FF HCM for example). I'm not sure I understand what you are driving at there... |
Tyler Mowbrey - 6 years ago
For those looking, I just found an old article from 2009 that shows how a trigger could be built to roll your own conversions: http://www.force2b.net/index.php/2009/01/sfc-multi-currency-improvement/ |
Pierre-Emmanuel DEV - 6 years ago
I do not undestand why the functionality implemented for Opportunities is not reported on Quotes & Orders. These are objects with similar structures and directly related in the purchasing process. |
Pierre-Emmanuel DEV - 6 years ago
I do not undestand why the functionality implemented for Opportunities is not reported on Quotes & Orders. These are objects with similar structures and directly related in the purchasing process. |
Dean De-Viell - 5 years ago
Is unbelievable we can create currency fields on custom objects but the rates can't be dated to a specific time, with the pound being rubbish currently this makes reporting and our data in general a total nonsense.