<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Fariz Rzayev on Medium]]></title>
        <description><![CDATA[Stories by Fariz Rzayev on Medium]]></description>
        <link>https://medium.com/@farrza111?source=rss-2ab7655b59bc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gO1vjoMVchF9O6Vc4hCdDQ.jpeg</url>
            <title>Stories by Fariz Rzayev on Medium</title>
            <link>https://medium.com/@farrza111?source=rss-2ab7655b59bc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:40:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@farrza111/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing Effective Dashboards and Power BI Optimization Techniques]]></title>
            <link>https://medium.com/@farrza111/designing-effective-dashboards-and-power-bi-optimization-techniques-1af86a8665d6?source=rss-2ab7655b59bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1af86a8665d6</guid>
            <category><![CDATA[power-bi-design]]></category>
            <category><![CDATA[dax-power-bi]]></category>
            <category><![CDATA[power-bi]]></category>
            <category><![CDATA[power-bi-dashboard]]></category>
            <dc:creator><![CDATA[Fariz Rzayev]]></dc:creator>
            <pubDate>Sat, 09 Nov 2024 21:10:22 GMT</pubDate>
            <atom:updated>2024-11-10T21:47:00.449Z</atom:updated>
            <content:encoded><![CDATA[<p>Visualizations are essential for simplifying decision-making, offering clear, actionable insights that documents or spreadsheets often lack. When tailored to stakeholder needs, dashboards become powerful tools for driving data-informed decisions. Below, I will outline foundational steps for designing an impactful, data-driven dashboard and share best practices for optimizing Power BI DAX measures to ensure efficiency and clarity.</p><blockquote><strong>Key Steps in Designing an Impactful Dashboard</strong></blockquote><ol><li><strong>Define the Scope</strong><br>Clarify the dashboard’s purpose. What business question or objective will it address?</li><li><strong>Identify the Audience</strong><br>Determine who will use the dashboard, tailoring design and functionality to suit their needs.</li><li><strong>Establish Decision-Making Goals</strong><br>Understand the types of decisions stakeholders will make by reviewing the dashboard, guiding your selection of metrics and visuals.</li><li><strong>Consider Calculations and Methodologies</strong><br>Determine any specific calculations or methodologies needed early on.</li><li><strong>Select the Right Visualizations</strong><br>Discuss visualization preferences with stakeholders to ensure intuitive, valuable insights.</li><li><strong>Set Key Performance Indicators (KPIs)</strong><br>Identify primary KPIs to be included in the dashboard. Focus on those that directly support decision-making.</li><li><strong>Decide Update Frequency</strong><br>Establish how often the dashboard will be updated (e.g., monthly, weekly, daily) based on data availability and user needs.</li><li><strong>Understand Data Sources and SLAs</strong><br>Familiarize yourself with data sources and Service Level Agreements (SLAs). Knowing the data refresh intervals and planning ingestion dates accordingly ensures timely updates.</li><li>After creating the dashboard and making a demo session to stakeholders, prepare a clear SOP (Standard Operational Procedure) for users to be able to utilize the dashboard in an effective way.</li></ol><blockquote><strong>Power BI Optimization: Design Patterns for Efficiency</strong></blockquote><p>Creating an optimized Power BI dashboard requires a strong data model before jumping into visualization. A well-structured model not only enhances accuracy but also boosts performance. Here are essential practices:</p><ol><li><strong>Create a Dedicated Date Table</strong><br>Build a comprehensive date table with sequential logic for handling dates. Establish relationships from this table to the fact table, following a one-to-many structure. This setup is key for robust time-based analysis.</li><li><strong>Maintain Appropriate Granularity</strong><br>Avoid increasing granularity in the fact table. Instead, extend the date table with ISO weeks, year-month sequences, holidays, and other time-based intelligence.</li><li><strong>Minimize Calculated Columns</strong><br>Calculated columns might seem like a quick fix, but they often lead to inefficiencies, complexity, and slow performance. Only use calculated columns in exceptional cases. Whenever possible, rely on optimized DAX measures for calculations.</li><li><strong>Start with a Solid Model </strong><br>A well-designed model is the foundation of an effective dashboard. Usually, people are jumping over the design part right away before sleeping over the data modeling part. However, it’s absolutely a wrong way because result will not be as accuracte as it should be unless the model is created properly. Carefully constructed relationships — especially between dimension and fact tables — ensure accurate and high-performance visualizations. If you don’t do it, then you can manually analyze the complexity of the model in DaxStudio and see how the granlarity increase time and space compexity as well. (I’ll post a seperate data modeling article as to relationships)</li></ol><p>By following these principles, you’ll build Power BI dashboards that are visually engaging, efficient, and scalable — providing stakeholders with the insights they need to make informed decisions.</p><blockquote><strong><em>I will share my design patterns that I have built over the course of my Power BI journey.</em></strong></blockquote><p>master calculations for the date table</p><pre>// Calculate the week ID based on the week number and year<br>WeekID = WEEKNUM(Sales_Table[Date], 1) + (YEAR(Sales_Table[Date]) - _MinYear) * 53<br><br>// Calculate the ISO week sequence<br>ISO_Week_Sequence = INT((Sales_Table[Date] - 2) / 7)<br><br>// Calculate the year-month sequence as a numeric identifier<br>Year_Month_Sequence= YEAR(Sales_Table[Date]) * 12 + MONTH(Sales_Table[Date]) - 1<br><br>// Generate a concatenated year and month identifier<br>YearMonth = YEAR(Sales_Table[Date]) * 100 + MONTH(Sales_Table[Date])<br><br>// Create a date key in YYYYMMDD format<br>DateKey = INT(YEAR(Sales_Table[Date]) * 10000 + MONTH(Sales_Table[Date]) * 100 + DAY(Sales_Table[Date]))<br><br>// Sequential day number<br>Sequential_Day_Number = INT(Sales_Table[Date])<br><br>// Determine if the day is a working day (Monday to Friday)<br>Working_Day = <br>    VAR isWorkingDay = WEEKDAY(Sales_Table[Date], 1) IN { 2, 3, 4, 5, 6 }<br>    RETURN isWorkingDay</pre><p>Previous Month (PM)</p><pre>// Calculate sales metric for the previous month<br>Previous_Month_Sales = <br><br>// Define the previous month&#39;s sales by shifting the current month sequence by -1<br>VAR previous_month_sales = CALCULATE(<br>    [Sales_Metric], <br>    FILTER(<br>        ALL(Sales_Date_Table), <br>        Sales_Date_Table[Year_Month_Sequence] = current_month_sequence - 1<br>    )<br>)<br><br>RETURN previous_month_sales</pre><p>Month over Month Delta</p><pre>// Calculate the difference in the sales metric between the current and previous month<br>MoM = <br><br>VAR current_month_sales = CALCULATE(<br>    [Sales_Metric], <br>    FILTER(<br>        ALL(Sales_Date_Table), <br>        Sales_Date_Table[Year_Month_Sequence] = current_month_sequence<br>    )<br>)<br><br>// Calculate the sales metric for the previous month<br>VAR previous_month_sales = CALCULATE(<br>    [Sales_Metric], <br>    FILTER(<br>        ALL(Sales_Date_Table), <br>        Sales_Date_Table[Year_Month_Sequence] = current_month_sequence - 1<br>    )<br>)<br><br>// Return the difference in sales between the current and previous month<br>RETURN current_month_sales - previous_month_sales</pre><p>Month over Month %</p><pre>// Calculate the Month-over-Month (MoM) percentage change<br>MoM_Percent = <br><br>// Get the latest month sequence across all selected data<br>VAR latest_month_sequence = CALCULATE(<br>    MAX(Sales_Date_Table[Year_Month_Sequence]), <br>    REMOVEFILTERS(Sales_Date_Table)<br>)<br><br>// Get the current month sequence based on the filtered context<br>VAR current_month_sequence = MAX(Sales_Date_Table[Year_Month_Sequence])<br><br>// Check if the latest month sequence matches the current month sequence<br>RETURN IF(<br>    latest_month_sequence &lt;&gt; current_month_sequence, <br><br>    VAR current_month_sales = CALCULATE(<br>        [Sales_Metric], <br>        FILTER(<br>            ALL(Sales_Date_Table), <br>            Sales_Date_Table[Year_Month_Sequence] = current_month_sequence<br>        )<br>    )<br><br>    // Calculate the sales metric for the previous month<br>    VAR previous_month_sales = CALCULATE(<br>        [Sales_Metric], <br>        FILTER(<br>            ALL(Sales_Date_Table), <br>            Sales_Date_Table[Year_Month_Sequence] = current_month_sequence - 1<br>        )<br>    )<br><br>    // Calculate the difference in sales between the current and previous month<br>    VAR month_sales_difference = (current_month_sales - previous_month_sales)/ previous_month_sales<br><br>    RETURN month_sales_difference<br>)</pre><p>Year over Year %</p><pre>// Calculate the Year-over-Year (YoY) percentage change<br>YoY_Change = <br><br>// Get the current month sequence based on the filtered context<br>VAR current_month_sequence = MAX(Date_Table[Year_Month_Sequence])<br><br>// Calculate the metric value from the same month in the previous year<br>VAR previous_year_metric_value = CALCULATE(<br>    [Metric_Result], <br>    FILTER(<br>        ALL(Date_Table), <br>        Date_Table[Year_Month_Sequence] = current_month_sequence - 12<br>    )<br>)<br><br>// Calculate the metric value for the current month in the current year<br>VAR current_year_metric_value = CALCULATE(<br>    [Metric_Result], <br>    FILTER(<br>        VALUES(Date_Table[Year_Month_Sequence]), <br>        Date_Table[Year_Month_Sequence] = current_month_sequence<br>    )<br>)<br><br>// Calculate the year-over-year percentage change as a ratio of the difference<br><br><br>VAR year_over_year_change_percent = DIVIDE(<br>    (current_year_metric_value - previous_year_metric_value), <br>    previous_year_metric_value<br>)<br><br>RETURN year_over_year_change_percent</pre><p>Six-month Moving Average (MA)</p><pre><br>// Calculate the 6-month moving average of the sales metric<br>monthly_moving_avg = <br><br>// Get the current month sequence based on the filtered context<br>VAR current_month_seq = MAX(Sales_Date_Table[Year_Month_Sequence])<br><br>// Filter for the last 6 months, up to and including the current month<br>VAR filtered_months = FILTER(<br>    ALLSELECTED(Sales_Date_Table[Year_Month_Sequence]), <br>    Sales_Date_Table[Year_Month_Sequence] &lt; current_month_seq <br>    &amp;&amp; Sales_Date_Table[Year_Month_Sequence] &gt;= current_month_seq - 6<br>)<br><br>// Calculate the 6-month moving average if there are at least 6 months in the filtered data<br>VAR result = IF(<br>    COUNTROWS(filtered_months) &gt;= 6,<br>    CALCULATE(<br>        AVERAGEX(filtered_months, IF(ISBLANK([Sales_Metric]), 0, [Sales_Metric])), <br>        ALLSELECTED(Sales_Date_Table)<br>    )<br>)<br><br>RETURN result</pre><blockquote>Mastering these techniques is an ongoing journey. As you continue developing dashboards and exploring advanced DAX functions, you’ll refine your ability to create powerful analytics tools that drive business success. Happy analyzing!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1af86a8665d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>