Identifying & Optimizing DAX Patterns (Case-Study)

Walk through a client case-study with me as I identify and optimize repeating DAX patterns. The end result having less lines of code, simpler logic, and faster performance. Tune in to learn more!
BECOME A CHANNEL MEMBER 🎉
-- / @havensconsulting
CHECK OUT OUR MERCH STORE 👕
-- havens-consulting.creator-spr...
LET'S CONNECT! 🧑🏽‍🤝‍🧑🏽 🌟
-- / havensbi
-- / reidhavens
-- / havensconsulting
-- / havensconsulting
VIDEO CHAPTERS 🎥
0:00 - Start of Video
0:30 - Content Intro
HAVENS CONSULTING PAGES 📄
Home Page - www.havensconsulting.net
Blog -- www.havensconsulting.net/blog-...
Blog Files -- www.havensconsulting.net/blog-...
Files & Templates -- www.havensconsulting.net/files...
Consulting Services -- www.havensconsulting.net/consu...
Online Courses -- www.havensconsulting.net/onli...
Contact & Support - www.havensconsulting.net/conta...
EMAIL US AT 📧
[e-mail]
#PowerBI #powerplatform #microsoft #businessintelligence #datascience #data #dataanalytics #excel #powerapps #datavisualization #dashboard #bi #analytics #powerquery #dax #microsoftfabric #semanticmodel

[@scramiro1]

A good video (that I can´t see much on youtube) would be how you debug when a formula is not providing the number you seek. Some option:, use TOCSV to see the outupt table, dax query of the visual to see filter context, etc. How do you do this?

[@HavensConsulting]

I have an upcoming video to show examples of the DAX query view. Otherwise the video with Daniel Otykier where he walks through the DAX Debugger in Tabular Editor 3 is also fantastic :)
ruclips.net/video/m4g9BxcUf4U/видео.html

[@martinbubenheimer6289]

It's always good to be reminded of cleaning up the code. Did this change just optimize readability or does it also optimize performance?

[@HavensConsulting]

The clients fact table was only 50k rows so there wasn't enough data to actually get a MS change. But using DAX studio there were definitely fewer calls being ran since I was using fewer CALCUALTES and calling the same measure repeatedly was reduced. So a combo of both optimization and readability here.

[@DanielWeikert]

Did you see Performance improvement?

[@HavensConsulting]

The clients fact table was only 50k rows so there wasn't enough data to actually get a MS change. But using DAX studio there were definitely fewer calls being ran since I was using fewer CALCUALTE's and calling the same measure repeatedly was reduced. So a combo of both optimization and readability here.

[@Nalaka-Wanniarachchi]

Nice case study,But it's always better to remember that variables are getting fixated before return statement.

[@HavensConsulting]

Good reminder, in the example I ran all the calculations are being ran before the return statement. So now calculation issues with this. Generally it's when you need to apply additional filters on a VAR that you need to consider where to apply the filter (during/after) declaring a VAR