Forum Discussion
Resolver ISAMEPERIODLASTYEAR expects a contiguous selection
Resolver IThanks for the responses everyone. amitchandak v-deddai1-msft i already checked that... Am I missing something obvious?
Community SupportHello @StephenK ,
Could you check the relationship between Fact_Schedule and Date Dim? Must be unidirectional 1- Many.
As a workaround, you can avoid using the time intelligence feature. See https://community.powerbi.com/t5/Desktop/Function-SAMEPERIODLASTYEAR-expects-a-contiguous-selection-Issue/m-p/583072
Best regards
Dedmon Dai
- StephenK
v-deddai1-msft I've already checked that. Please see my previous screenshot for verification. I've looked into the workaround you suggested. I'm not finding a good application for it because I need my SAMEPERIODLASTYEAR measure to be visualized by month.
This is a very late response but I just resolved a near identical issue and felt it should be documented.
The problem is actually the bidirectional filter on your Holidays and COVID19_Schedule tables that connect to your Date table, even though those tables aren't necessarily involved in the calculation. Being a one-to-one relationship forces bidirectional filtering, so switch that to be a many-to-one relationship so you can mark the cross filter direction as single.
I had a very similar situation with a holiday table connecting to a date table:
Measures using SAMEPERIODLASTYEAR failed until I made this minor change, now those measures calculate properly:
Syndicate_AdminAdministrator
Thank you so much for your help! With this I discovered the problem I had in a model that was not doing the calculation for me
