Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi Community,
I need your help. I’m building a Power BI pipeline using data from Salesforce. For FX rates, I’m using the Dated Conversion Rate object, but the values I’m getting don’t match the Salesforce report. The difference is small, but my finance team won’t accept the discrepancy.
Has anyone faced this issue before? Can you help me come up with a method to make sure the values in Power BI match exactly what’s in Salesforce?
Thanks in advance!
Solved! Go to Solution.
Hi @SBertozzo77
Hi,
This type of mismatch is pretty common, even if the difference is small. A few things to check:
Data source mismatch
The Salesforce report might not be using the DatedConversionRate object directly. It could be using a custom rate table or a snapshot entered manually.
Time zone or refresh timing
Even a few hours difference between the Salesforce report and your Power BI refresh can cause discrepancies, especially on days with high FX volatility.
Calculated logic in the Salesforce report
Sometimes rates are applied indirectly using formulas, triggers, or Apex logic. Make sure you're not comparing raw data to derived values.
Rounding or formatting
Power BI might be rounding or trimming decimals. Check the exact precision being used on both sides.
What you can do:
Export the Salesforce report as CSV and compare it directly in Power BI, including the currency pair and rate date.
Make sure you're pulling the exact version of the rate table used in the report — not just assuming it's DatedConversionRate.
If needed, build a validation table in Power BI that compares expected vs. actual values, and send that to Finance.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
Salesforce can use different exchange rates based on, say, Opportunity Close Dates.
Pinpoint specific examples - Opportunities and Close Dates - where the result matches and where they don't.
Then reach out to your IT guys in charge of Salesforce and find out what they're using (say, one rate for 2024 and another for 2025).
Once you have the exact rules, you can replicate them in PBI.
Hi @SBertozzo77
Hi,
This type of mismatch is pretty common, even if the difference is small. A few things to check:
Data source mismatch
The Salesforce report might not be using the DatedConversionRate object directly. It could be using a custom rate table or a snapshot entered manually.
Time zone or refresh timing
Even a few hours difference between the Salesforce report and your Power BI refresh can cause discrepancies, especially on days with high FX volatility.
Calculated logic in the Salesforce report
Sometimes rates are applied indirectly using formulas, triggers, or Apex logic. Make sure you're not comparing raw data to derived values.
Rounding or formatting
Power BI might be rounding or trimming decimals. Check the exact precision being used on both sides.
What you can do:
Export the Salesforce report as CSV and compare it directly in Power BI, including the currency pair and rate date.
Make sure you're pulling the exact version of the rate table used in the report — not just assuming it's DatedConversionRate.
If needed, build a validation table in Power BI that compares expected vs. actual values, and send that to Finance.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
You might want to reach out to your SFDC dev/admin to help you locate the right object for the Salesforce report.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 51 | |
| 40 | |
| 37 | |
| 14 | |
| 14 |
| User | Count |
|---|---|
| 85 | |
| 69 | |
| 38 | |
| 29 | |
| 27 |