A follow-up on implementing Like-for-Like (L4L) analysis for retail stores in Power BI, addressing a confusing edge case where PY (prior year) values were assigned to different L4L states than current-year values. The fix involves adding a second L4LKey_PY column built via a SQL cursor procedure that compares store

6m read timeFrom towardsdatascience.com
Post cover image
Table of contents
IntroductionThe issueThe solutionConclusionReferences

Sort: