Visual & Report-Scoped Measures

**On screen:** Hero title card: "Visual & Report-Scoped Measures" with subtitle and tagline listing Dynamic Titles, Conditional Formatting, SVG Visuals, Filter Measures, Display Strings - Welcome the audience and set the stage: this guide covers a layer of DAX most people overlook - Frame the core idea early: there are measures that drive business logic, and measures that drive how a report *looks* - Mention the "Report-Scoped Presentation Layer" badge: this is the mental model for the entire guide *Transition:* "Let's start by defining exactly what we mean by report-scoped measures versus semantic model measures."

**On screen:** Semantic Model Measures card: "What the business needs to know" with examples: Sales, Profit, Margin %, YTD calculations, KPIs - These are the measures everyone thinks of first: core business logic, reusable across all connected reports - Emphasize the word *reusable*. These live in the model and any report connecting to it gets them automatically - Examples audience already knows: Sales, Profit, Margin %, YTD calculations *Key message:* Semantic model measures answer the question "What does the business need to know?". They are the single source of truth.

**On screen:** Report-Specific Measures card: "How the report presents information" with examples: Titles, colors, SVG images, display formatting - These measures control *presentation*, not calculation. They make reports look polished and professional - They are scoped to a single report because their formatting logic is not reusable across other reports - Give a quick example: a dynamic chart title that shows "Sales by [Region] | Dec 2025" is presentation, not business logic *Transition:* "Now that we see the distinction, let's explore the six types of report-scoped measures you'll encounter."

**On screen:** Dynamic Titles & Subtitles card: DAX using SELECTEDVALUE and FORMAT(TODAY()), output preview showing "Electronics Sales | Dec 2025" - Walk through the DAX pattern: SELECTEDVALUE grabs the slicer selection, FORMAT adds a timestamp - Stress the fallback parameter: "All Categories" when nothing or multiple items are selected - Use cases: context-aware chart titles, "Showing data for: [Region]", last refresh timestamps - This is usually the first report-scoped measure people create. It is the gateway to the others *Transition:* "Titles tell users what they're looking at. Next: colors tell them how to feel about it."

**On screen:** Conditional Formatting Measures card: DAX returning hex color codes, table preview with green/red variance indicators - These measures return hex color strings that Power BI uses for background, font, or icon formatting - Point out the demo table: North is green (+12.4%), South is red (-3.2%). Users instantly understand status - Key nuance: the measure returns a *string* like "#00875A", not a number. This trips people up - Use cases: traffic light indicators, threshold-based coloring, brand color application *Transition:* "Colors are powerful, but what if you need actual graphics inside a table? That's where SVG measures come in."

**On screen:** SVG Image Measures card: DAX returning data URI strings, demo table with inline bullet charts showing bars and target lines - This is the most visually impressive type. You can embed bullet charts, sparklines, and icons directly in table cells - Walk through the pattern: the measure returns a data URI string that Power BI renders as an image - Point out the demo: Widgets at 85% of target (green bar), Gadgets at 65% (orange bar) with target lines - Mention the gotcha early: you must set the Data Category to "Image URL" or it shows raw text *Key message:* SVG measures turn boring tables into information-rich dashboards without needing extra visuals.

**On screen:** Visual-Scoped Filter Measures card: DAX using RANKX for Top N filtering, side-by-side demo showing filtered vs. unaffected visuals - These return TRUE/FALSE and act as visual-level filters without affecting other report elements - Walk through the demo: "Top 5 Products" visual is filtered by the measure, but the "All Products Total" card still shows 247 - This is *scoped* filtering. The filter only applies where you put it - Use cases: Top N filtering, threshold filters, show/hide logic *Transition:* "Filters control what appears. Display strings control how values are presented to users."

**On screen:** Display String Measures card: DAX combining Sales value with variance percentage, output preview showing "$4.2M (+8.3%)" - These combine multiple values, units, or context into a single formatted text output - Walk through the pattern: FORMAT the value, concatenate with the variance percentage in parentheses - Great for card visuals where you want to show a primary metric plus context in one measure - Other patterns: "Showing 42 of 156 items", "Q3 2024 vs Q3 2023", combined metric cards *Transition:* "The last standard type focuses on user experience: tooltips and accessibility."

**On screen:** Tooltip & Accessibility Measures card: DAX using UNICHAR(10) for line breaks, tooltip preview with Sales/Target/Variance - These return descriptive text for tooltips or screen reader alt-text - Point out UNICHAR(10). This creates line breaks within a single measure, essential for multi-line tooltips - The demo shows a rich tooltip: Sales, Target, and Variance on separate lines with a checkmark - Accessibility angle: alt-text measures make Power BI reports more inclusive for screen reader users *Transition:* "There's one more type that deserves special mention: Visual Calculations."

**On screen:** Visual Calculations honorable mention card: purple theme, RUNNINGSUM and % of Total examples, table with data bars showing Running Total and percentage - Visual Calculations are special: they *must* be report-scoped because they can only exist within a visual - Unlike the other six types where you *choose* to keep measures in the report, Visual Calculations have no choice - Walk through the demo table: Running Total accumulates row by row, % of Total shows each region's share - Mention the unique functions: RUNNINGSUM, MOVINGAVERAGE, PREVIOUS, NEXT, COLLAPSE, EXPAND - These are relatively new in Power BI and are still evolving *Key message:* Visual Calculations are the only type that is *inherently* report-scoped. All others are a design choice.

**On screen:** "Clean Field List" card with checklist icon: explanation about keeping the semantic model focused - First reason: report builders see only business metrics, not formatting helpers - Imagine a model with 200 measures where 60 are formatting helpers. That is overwhelming and confusing - Keeping presentation measures in the report means the semantic model stays lean and purposeful *Key message:* A clean field list is a sign of a well-designed semantic model.

**On screen:** "Avoid Confusion" card with question mark icon: preventing users from misusing formatting measures - Second reason: users won't accidentally drag [Title Measure] or [Variance Color] into a chart's values field - This happens more than you'd think. A user sees a measure called "Color - Status" and tries to analyze it - Clear separation prevents support tickets and confusion *Transition:* "It also makes your life easier when things need to change."

**On screen:** "Easier Maintenance" card with wrench icon: updating formatting in one place - Third reason: visual measures stay with their reports, not scattered across the model - When a report needs a formatting change, you edit it in the report. There is no risk of breaking other consumers - This is especially important in organizations with multiple reports connected to one semantic model *Transition:* "This separation also helps your end users work more confidently."

**On screen:** "Self-Service Friendly" card with users icon: giving report creators clear, trustworthy metrics - Fourth reason: report creators get obvious, reliable metrics they can trust - Self-service BI depends on users feeling confident about what they're using. Cluttered field lists erode that confidence - No risk of someone building a critical dashboard on a formatting measure *Key message:* Good architecture makes self-service actually work.

**On screen:** "Report Portability" card with layout icon: semantic model stays clean and reusable - Fifth reason: central reports own their visual logic while the semantic model stays universally reusable - If you need to rebuild or duplicate a report, the presentation measures travel with it - The semantic model remains a stable, shared foundation *Transition:* "Now that we know why. Let's talk about how to keep these measures organized."

**On screen:** Display Folders card: folder tree showing Report Measures with subfolders for Titles, Formatting, and SVG - First strategy: use Display Folders to group report measures by function - Create a top-level "Report Measures" folder, then subfolders: Titles, Formatting, SVG - This mirrors how you'd organize files on disk, intuitive and immediately scannable - Subfolders are set in the Properties pane of each measure *Key message:* Display Folders are the single most effective organizational tool in Power BI.

**On screen:** Naming Conventions card: prefix list showing Title -, Color -, SVG -, Filter -, Display - - Second strategy: use type prefixes so the purpose of each measure is immediately obvious - Walk through the prefixes: Title -, Color -, SVG -, Filter -, Display - - Consistency is key. Pick a convention and document it for the team - Prefixes also make alphabetical sorting more useful since related measures cluster together *Transition:* "And for measures that users shouldn't interact with directly, there's a third strategy."

**On screen:** Hide in Report View card: list showing Sales and Profit as visible, Color and SVG measures as hidden - Third strategy: right-click a measure and select "Hide in report view" - Hidden measures still work in conditional formatting and title expressions. They just don't clutter the field list - This is the finishing touch: folders organize, prefixes clarify, hiding declutters - Note: hidden measures show as greyed out in the model view so developers can still find them *Key message:* Combine all three strategies for maximum clarity: folders + prefixes + hide from end users.

**On screen:** "Use a Dedicated Measures Table" tip: create a disconnected table specifically for report-level measures - Pro tip: create a table like "Report Measures" that has no relationships to any other table - This completely isolates presentation logic from the data model structure - The table can be as simple as a single-column table with one row. It is just a container for measures *Key message:* A disconnected measures table is the cleanest architectural pattern for report-scoped measures.

**On screen:** "Test SVG in a Card First" tip: debug SVG measures in a card visual before scaling to tables - SVG measures can be tricky to debug because errors show as blank cells in tables - Start with a card visual where you can see the full output and iterate quickly - Once the data URI renders correctly in a card, move it to your table or matrix *Transition:* "Debugging is easier when you can see the full output."

**On screen:** "Document Your Naming Convention" tip: establish and share prefixes with your team - Documentation is the bridge between a good convention and a convention that actually gets followed - Write it down, share it in a team wiki or README, and enforce it in code reviews - Consistency across a team is worth more than the "perfect" naming scheme *Key message:* The best naming convention is the one everyone actually uses.

**On screen:** "Avoid Hardcoded Colors" tip: use variables or a color lookup table instead of hex values - Hardcoded hex values like "#00875A" scattered across 20 measures are a maintenance nightmare - Use a disconnected color table or DAX variables to define your palette in one place - When the brand colors change, you update one table instead of hunting through every measure *Transition:* "Performance matters too, especially with formatting measures."

**On screen:** "Keep Format Strings Simple" tip: minimize FORMAT() calls and string concatenation in high-cardinality contexts - FORMAT() is one of the more expensive DAX functions, especially at scale - In a table with thousands of rows, a complex FORMAT call on every row adds up - Pre-calculate values where possible and keep concatenation minimal *Key message:* Report-scoped measures should enhance the experience, not degrade performance.

**On screen:** "Use UNICHAR() for Line Breaks" tip: UNICHAR(10) for line breaks, UNICHAR(9) for tabs - UNICHAR(10) is the newline character. It is essential for multi-line tooltips and display strings - UNICHAR(9) adds tab spacing for aligned columnar output - UNICHAR(10) is the one thing most people skip in tooltip measures. It is also what separates a tooltip from a wall of text *Transition:* "Before we wrap up, let's cover the mistakes people make most often."

**On screen:** "SVG Image URL Data Category" gotcha card: most common SVG issue explained - This is the number one question people ask: "Why does my SVG measure show raw text?" - The answer is almost always: the Data Category is not set to "Image URL" in the modeling view - Walk them through: select the measure, go to Properties, set Data Category to Image URL - This is a one-time setting per measure but it is easy to forget *Key message:* If your SVG shows text instead of an image, check the Data Category first. It solves the problem 90% of the time.

**On screen:** "Conditional Formatting Hex Format" gotcha card: hash symbol requirement - Color hex codes *must* include the hash (#) symbol - Returning "00875A" instead of "#00875A" silently fails. Power BI just ignores it - Easy to miss because there is no error message, the formatting simply does not apply *Transition:* "Another silent failure involves SELECTEDVALUE."

**On screen:** "SELECTEDVALUE Returns BLANK()" gotcha card: fallback parameter importance - SELECTEDVALUE returns BLANK when multiple items or no items are selected - Without a fallback, your dynamic title just shows nothing. A blank chart title looks broken - Always use the second parameter: SELECTEDVALUE(Table[Col], "All Items") - Test with multi-select slicers to catch this during development *Key message:* Always provide a meaningful fallback for SELECTEDVALUE in title measures.

**On screen:** "Filter Measures and Totals" gotcha card: total row removal issue - Visual-level filter measures that return TRUE/FALSE can accidentally remove the total row - The total row evaluates the filter measure in a context where HASONEVALUE is FALSE, so the filter returns FALSE - Fix: add an ISINSCOPE() or HASONEVALUE() check to always include totals - This is subtle because the table looks fine until someone notices the missing grand total *Transition:* "Let's end with a quick reference table that summarizes everything we've covered."

**On screen:** Quick Reference Table: all six types plus Visual Calculations, showing what each returns, where it's used, and an example - Use this as a summary and takeaway. It distills the entire guide into one scannable table - Walk through each row briefly: Dynamic Titles return text, Conditional Formatting returns hex, SVG returns data URIs, etc. - Note the asterisk on Visual Calculations. They are the only type that *must* be report-scoped - Encourage the audience to screenshot or bookmark this table as a daily reference *Key message:* Separating presentation logic from business logic is a small architectural decision that that keeps field lists clean, reports portable, and colleagues from accidentally analyzing color hex codes.