IGLOO BI

What distinguishes a "pro" from an "intermediate" user in Power BI? It is whether they understand and use functions based on their intrinsic roles. While many users try to handle both filter removal and table creation using only the ALL function, in the world of large-scale models, this slight ambiguity leads to maintenance nightmares and performance bottlenecks. In 2019, Microsoft introduced the dedicated tool REMOVEFILTERS for very clear reasons: Intent: Is the calculation logic immediately clear upon reading the code? Structure: Is it preventing the unnecessary creation of virtual tables? Performance: Can the engine modify the filter context in the most efficient way? Beyond a simple syntax comparison, discover how to use REMOVEFILTERS to complete the aesthetics of your DAX design.   1. Historical Background: An Evolution That ALL Could Not Handle Alone 1) ALL – The "Solitary Founding Member" of the Power Pivot Era The ALL function was introduce...

DAX Optimization Technique: Execution-Aware DAX Design When a Power BI report is slow, most users suspect the following: Is it because the data volume is too large? Is the visualization too complex? Are functions like SUMX or CALCULATE too heavy? However, the real cause most frequently encountered in practice is something else entirely: the developer is unaware that the engine is performing unnecessary calculations "until the very end." This post addresses exactly that point. Today, we will explore "Execution-Aware DAX Design"—the core of DAX performance optimization—and the "Early Exit" technique, which physically removes unnecessary operations.   1. Why Does DAX Calculate Useless Things Until the End? DAX is inherently a language that "seeks to preserve meaning." While general programming decides its path based solely on the "current value," DAX is a perfectionist that considers data relationships and every possible change. Let’s u...

The first step to mastering DAX is understanding the "identity of a value." You must clearly define whether what you are creating is "fixed historical data" or a "real-time response" that changes based on a user's question. 1. Calculated Column: A Fixed State Determined at Data Loading A Calculated Column is computed row by row during the data refresh process and is physically stored as a value within the data model. Once calculated, it does not change based on slicers or filters in the report. Calculation Timing: Performed only once during the data refresh. Operating Principle (Row Context): It scans each row one by one and completes the calculation using only the values present in that specific row. System Characteristics: Slicers or filters on a report cannot change the "result value" of a Calculated Column. Slicers merely determine "which rows to show" (Visibility). Primary Uses: Values to be used as slicer items (e.g., Age Gr...

When executives look at a weekly dashboard and ask, "Wait, why is this number different from last week?" a cold sweat runs down your spine. It would be a relief if an error message actually popped up. The truly terrifying situation is when the data looks perfectly fine, but the report is quietly outputting the wrong numbers. Today, we will dive into two types of "Silent Errors" that can instantly destroy your report's credibility and explore their solutions from a practical perspective. Related Anti-Patterns BLANK Anti-Pattern 5: Silent Error Masking BLANK Anti-Pattern 7: Filter Context Conflict While these two patterns differ in nature, they lead to the same disastrous conclusion: "The report looks normal, but the decision-making is wrong."   1. Data Reliability: The Invisible Crack Anyone can notice when a report breaks, allowing for immediate fixes. However, when a report appears normal but data-driven decisions are flawed, the entire organization s...

   When a Power BI report starts lagging, most people immediately suspect the data volume or the number of visuals. However, in practice, performance degradation often stems from very small DAX design choices. A prime example is measures that perform unnecessary calculations until the very end. Performance Issues are Discovered Later Than "Wrong Results" As seen in [Mastering BLANK Part 3-2], issues with incorrect totals are noticed relatively quickly. Performance issues are different: At first, it just feels "a little slow." As data grows and pages get complex, the lag becomes tangible. Eventually, the screen freezes every time a slicer moves, and users lose trust in the report. By this point, the report often has a structure that was destined to be slow from the design stage. Related Anti-Patterns BLANK Anti-Pattern 4: Performance Killer BLANK Anti-Pattern 6: Redundant Calculation The commonality between these two patterns is clear: "Calculating to the end ev...