topic Re: Problem with SAMEPERIODLASTYEAR in DAX Commands and Tips

Problem with SAMEPERIODLASTYEAR

peluca — Fri, 21 Feb 2020 22:44:34 GMT

After creating a dimdate table I tried to calculate a measure by using SAMEPERIODLASTYEAR but it does not work.

calculate(([Unid Actual]),SAMEPERIODLASTYEAR((DimDate[Date])))

Re: Problem with SAMEPERIODLASTYEAR

vivran22 — Sat, 22 Feb 2020 02:47:14 GMT

What is the structure of your data table? Also, I am hoping you have created the relationship between the date of your fact table and the calendar table.

I have recreated the scenario with a sample data:

And created a calendar table:

Calendar = ADDCOLUMNS ( CALENDAR ( MIN ( dtTable[Order Date] ), MAX ( dtTable[Order Date] ) ), "Year", YEAR ( [Date] ), "Month", DATE ( YEAR ( [Date] ), MONTH ( [Date] ), 1 ) )

And mark it as a date table.

Created the relationship:

Created measures:

Total Orders = SUM(dtTable[Order Quantity]) PY Orders = CALCULATE ( [Total Orders], SAMEPERIODLASTYEAR ( 'Calendar'[Date] ) )

Getting the results in visual:

Regards,
Vivek

If it helps, please mark it as a solution

Kudos would be a cherry on the top 🙂

https://www.vivran.in/

Re: Problem with SAMEPERIODLASTYEAR

Anonymous — Sat, 22 Feb 2020 11:36:27 GMT

It does work if you do it as it should be done. vivran22 has the right solution. For the time-intel functions to work correctly, you have to have a date table that has been marked in the model as DATE TABLE and connected to the facts/dims. Nothing more.

Re: Problem with SAMEPERIODLASTYEAR

peluca — Tue, 25 Feb 2020 15:23:04 GMT

Thanks so much for your help!!

I had an issue regarding the format of my dimdate table