IGLOO BI

In our previous post, we explored how to calculate Year-over-Year (YoY) growth using the OFFSET function, and how to combine it with PARTITIONBY to prevent reference errors when monthly data is missing. This time, we will examine INDEX , another core function available within Visual Calculations. While OFFSET is a function that navigates to a relative row based on the current position, INDEX is a function that directly references a row at a specified sequence number. This is highly useful for analyses that require comparing against a fixed baseline data point or finding starting and ending points. In this article, we will unpack the operational mechanics of the INDEX function alongside a YoY calculation example, and summarize the critical production-grade limitations that you must understand in practice. Previous post Calculating Year-over-Year (YoY) Growth Using SUMX + FILTER in the New Power BI Visual Calculations Calculating Yea...

In our previous two posts, we explored how to calculate Year-over-Year (YoY) growth utilizing Power BI’s innovative new feature, Visual Calculations. • First Post: We examined how to deploy ROWS and SUMX to directly navigate and locate prior-year same-month data within the current visual. • Second Post: We implemented the identical analytical result by leveraging the WINDOW function to reference data exactly 12 rows prior relative to the current row. However, within Visual Calculations, there are other highly potent functions belonging to the Window Function family besides WINDOW. These are OFFSET and INDEX. In many practical scenarios, OFFSET is vastly more intuitive than WINDOW, and INDEX becomes far more useful when you need to pinpoint an absolute position. In this article, we will completely implement the identical Year-over-Year (YoY) growth metric...

In our previous discussion, we calculated Year-over-Year (YoY) growth by utilizing ROWS and SUMX to directly search for matching prior-year data within the current visual. However, the powerful capabilities of Visual Calculations do not end there. As Power BI has expanded this new feature set, we can now leverage Window Functions such as WINDOW, OFFSET, and INDEX. While the previous approach can be defined as "finding data via logic and conditions," utilizing a Window Function is "referencing data based on its relative position." Even though both methods produce identical results, the analytical lens and calculation mechanisms are fundamentally altered. To be frank, it is not strictly mandatory to deploy this method for your everyday YoY calculations. Nonetheless, the reason we must implement this function firsthand is clear: it broadens our data-mod...

When building production dashboards with Power BI, one of the most frequently implemented core metrics is Year-over-Year (YoY) growth. Traditionally, achieving this required combining complex DAX functions such as CALCULATE, SAMEPERIODLASTYEAR, and ALL. In particular, if the data model's relationships or Date Table configurations were not absolutely flawless, incorrect values would often surface—causing significant headaches for beginners and intermediate users alike. However, the introduction of the new 'Visual Calculation' feature in Power BI has completely changed the game. Instead of navigating through the entirety of a complex data model, users can now intuitively perform calculations by treating the visualization table (the visual) currently displayed on the screen as its own independent database. In this post, without relying on intricate time intelli...

When you first start using the new Visual Calculations feature in Power BI, you will surprisingly run into a bottleneck at the very beginning. This occurs precisely when attempting to deploy iterator functions such as SUMX, AVERAGEX, MAXX, and FILTER. Code that we used to take completely for granted in standard DAX suddenly stops working. SUMX(   Sales,   Sales[Qty] * Sales[Price] ) In a traditional measure, you simply needed to place the Sales table into the first argument. In a Visual Calculation, however, the exact moment you input a table name, an error is triggered. Initially, I assumed I was simply mistaken about the syntax. However, after days of testing various scenarios, I realized something fundamental: Visual Calculations operate on an entirely different paradigm from trad...