Forum Discussion
Keeping a fixed conversion rate while comparing current and previous year
In the end, to avoid the rate being impacted by SAMEPERIODLASTYEAR, I first calculate the PY amount in local currency. Then I apply the conversion, instead of relying on the already converted amount and using time intelligence functions. This approach fixes the issue.
Hi akim_no,
Thank you for sharing the PBIX. Since the report contains many measures and dependencies, instead of changing anything directly in your file, I first reproduced your scenario in a very small sample PBIX with just a few rows.
This made it easy to validate your requirement:
1.The conversion rate is taken only from the period selected in the date slicer.
2.That same fixed rate is applied when using SAMEPERIODLASTYEAR.
3.so the PY calculation no longer shifts to a different rate.
The sample confirmed that this logic works as expected.
Please let me know which measure you want us to adjust first.
Regards,
Community Support Team.
I think it worked for you because you are using a single currency. However, when working with multiple currencies and testing it on my data, it doesn’t work.
Even for the current value — the value of n — it doesn’t give the correct conversion.
In my file, what I’m trying to do is create the following measures ;
- Euro Amount,
- SelectedRate,
For the other ones, however (SelectedRate for test, PY Euro Amount choisen rate, Euro Amount Choisen rate), it allows me to test whether the conversion is applied using the rate I want to use.
Thank you
Hi akim_no,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Regards,
Community Support Team.