Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Up until now, SAMEPERIODLASTYEAR worked fine. I'm using it with a custom date table that has fiscal years, fiscal months, etc. The new issue seems to stem from our last fiscal year had 53 weeks whereas most years have 52 weeks. I created 2 measures named Sales Act (this year) and Sales PY (prior year). When I pull the 2 measures into a visual at the same time for October 2024 (6 weeks) vs. October 2023 (5 weeks), the data for October 2023 is not correct. It's close to double what it should be. However, when I compare October 2023 to October 2022, everything is correct. Also, If I just pull the months as actuals into a visual without any comparison, the data is correct for both October 2024 and October 2023. Any idea what's going on here?
If you have your own custom fiscal calendar then you always need to implement your own YoY calculation. ALWAYS.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.