Forum Discussion
SAMERPERIODLASTYEAR - Non Contiguous Date Selection Error
- 9 years ago
I get the same exact error message.
How about this instead of using SAMEPERIODLASTYEAR:
Fees Billed SPLY = CALCULATE([Fees Billed YTD],DATEADD(Table_BasicCalendarUS[DateKey],-1,YEAR))
I get the same exact error message.
- bblais9 years agoResolver III
I don't believe so or that it's necessary. I just always make sure my PK is an actual date column and not a key like 20170401 or something like that, as I've found many of the DAX capabilities won't work correctly if you don't use a date column when relating tables.
The only other thing I can think of for you to check is to see if there are other roundabout relationships between the date table and another table that then joins back to your fact table directly or indirectly. If there's any bi-directional relationship there, it might affect what you're trying to do even though your direct relationship between date and fact table is single...
- MojoGene9 years agoPost Patron
Is there a method in Power BI to confirm that a table is marked as a date table?
- brickhouse35398 years agoFrequent Visitor
I had this issue and changing the sameperiodlastyear from my year-month column to the full date column as suggested solved the issue, thanks!
- Anonymous6 years agoNot applicable
This is what I did to solve the issue.
- r_fioretti6 years agoHelper I
I had the same issue.
I had another table with an inactive relationship and still couldn't get a month over month view.
I only had it solved after delete the inactive relationship between the date table and other table.