Skip to main content
Solved

Currency rate error - Business Opportunity Pipeline

  • December 20, 2021
  • 4 replies
  • 127 views

Forum|alt.badge.img+10
  • Hero (Customer)
  • 96 replies

Hi All,

In Business Opportunity Pipeline window, I am getting the below error when I include in my filter Business Opportunities  with different currencies (AUD & NZD). 

Why is it using currency type 1, aren’t they suppose to use currency rate 3 ?

thanks 

Best answer by Gaveshi Maddegamage

In which environment you encountered this issue?

Since Business Opportunity is a sales side functionality, I believe it is the company’s Default Sell Currency Rate Type that is used in fetching data here.

So if your company 65 has currency rate type 1 defined as the Default Sell Currency Rate Type,  you should define  AUD to NZD rate under currency rate type 1.  Please add it and check whether the issue gets resolved.  

 

 

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

4 replies

Rasika Lakmal
Superhero (Customer)
Forum|alt.badge.img+18
  • Superhero (Customer)
  • 214 replies
  • December 20, 2021

@NMALKI You need to check for the currency rate type 1. Attached screenshot shows currency rate type 3.


Forum|alt.badge.img+10
  • Author
  • Hero (Customer)
  • 96 replies
  • December 21, 2021

@Rasika Lakmal screen attached . but why is it checking type 1 not 3 ? is it defined in another window to check type 1 ?

thanks 


Forum|alt.badge.img+3

In which environment you encountered this issue?

Since Business Opportunity is a sales side functionality, I believe it is the company’s Default Sell Currency Rate Type that is used in fetching data here.

So if your company 65 has currency rate type 1 defined as the Default Sell Currency Rate Type,  you should define  AUD to NZD rate under currency rate type 1.  Please add it and check whether the issue gets resolved.  

 

 

 


Forum|alt.badge.img+10
  • Author
  • Hero (Customer)
  • 96 replies
  • December 21, 2021

@Gaveshi Maddegamage  thanks for your clarification, it works :) 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings