web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Confusion about currency on lead/opportunity

(0) ShareShare
ReportReport
Posted on by 40

Hello, 

A customer is confused (and so am I) about how opportunities inherit their currency (transaction currency). 

They created a lead which got the users preferred currency (SEK). When they qualified the lead as "won" the resulting opportunity got currency "EUR" but the contact and account got "SEK". 

I have verified this by looking at the audit history of each record..

So my question therefore is: how could the opportunity get EUR as currency when the Lead it was created from has SEK and also the user performing the actions has SEK?

Below is my understanding of currency based on the article linked below (plus other resources and experience). According to this I believe that the opprtunity also should have gotten SEK..

-----------

  • A Dynamics Environment always has a default (base) currency. This will be the default currency for all records created.

 

  • If the Dynamics Environment has more than one currency configured all users default has the base currency unless they change this in their personal system settings.
    • If a user changes his/her default currency this will instead be the default currency for records created by that user.
      • Exception: if for example a parent record (f.e Account) is created in EUR but a user with default SEK creates an opportunity when standing on the parent record the Opportunity will inherit the currency from the parent record. The user may of course choose to change the currency for that record to any other configured currency.
      • In contrast of the above, if just creating a new opportunity from the opportunity view and later adding a parent record the currency of the opportunity will not automatically be inherited from the parent record.

 

  • For each field of type “Currency” there is a separate field, default hidden, that always stores the value in the systems base currency. This is useful when making reports.

 

  • Updating exchange rate dot not impact/recalculate currency fields in existing records. Only new records will use the updated exchange rate.

 

Source: https://neilparkhurst.com/2019/02/25/mb-210-microsoft-dynamics-365-for-sales-currencies/

I have the same question (0)
  • Suggested answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    Hello,

    Check the mapping between lead and opportunity - if currencies are different I believe it's not mapped. And if it was not mapped opportunity used Default Currency of the environment - is it default currency for the environment?

  • Fedorov Profile Picture
    40 on at

    Hello,

    On Lead entity I checked the 1:N relationship named "opportunity_originating_lead" and I can see that the field lead.transactioncurrencyid is mapped to field opportunity.transactioncurrencyid.

    The base currency of the system though is EUR..

    So I don't know if I got any wiser...

  • Suggested answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    That is weird. I will check that in my environment.

    As a workaround you can use following trick:

    1. Create realtime workflow that handles "Create" of opportunity.

    2. Check if originating lead field contains data. If it does not - stop the workflow.

    3. Update opportunity's currency with the currency from originating lead.

  • Fedorov Profile Picture
    40 on at

    Thanks, I will try that.

    I have managed to recreate the issue exactly as the Customer reported it.

    I set my own currency to SEK. I create a Lead. Lead gets SEK as currency. I then qualify the lead. The resulting opportunity gets EUR. The resulting Contact gets SEK..

    It is weird at this point..

  • Suggested answer
    Fedorov Profile Picture
    40 on at

    This has now been solved

    We use a custom javascript to initiate the qualification of the lead.

    Turns out it was the custom javascript setting the "opportunityCurrencyId" to null. This has the consequence that the opportunity gets the base currency of the system instead of any preferred currency on the user.

    So, to solve this make sure to explicitly set the currency to the same as on the lead record in the javascript code.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 81 Super User 2025 Season 2

#2
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 49 Most Valuable Professional

#3
#ManoVerse Profile Picture

#ManoVerse 40

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans