Forum Discussion
Help with Currency Conversion, Need to have Fixed Rate and Transaction Rate
I tried a different approach and it works well for handling transactions across different dates. The idea is to use time intelligence to shift the transactions while keeping the rate difference (fixed vs transaction) as a constant. This way, the transactions convert according to the desired date logic, and the rate difference variable simply determines whether the calculation uses the fixed rate or the transaction rate
Super UserHello,
It sounds like your filter context is shifting both fact and rate tables together, instead of separating them
one approach is to override the date filter only for the rates part of the measure, something like using CALCULATE with REMOVEFILTERS or ALL on the rate date, while keeping SAMEPERIODLASTYEAR (or your PY logic) on the transaction side, so basically you “freeze” the rate context to the slicer year and only let the transaction dates move.
Another option is to store the selected year in a variable and explicitly filter the rate table to that year inside the measure, so PY logic doesn’t touch it
if your model allows it, keeping rates in a disconnected table and applying them via TREATAS can also help avoid this kind of context bleed
Best regards,
Daniele
Thanks, you are correct that the filter context is shifting both the transactions and rate. I have tried many different ways but can't work out how to freeze the rate context.
The date table and rate table is already disconnected.