Barra de navegación
Cuando tengo un gráfico de barras, por lo general fechas (meses), la barra de desplazamiento podría configurarse para situarse siempre al final o al inicio del gráfico (idea), de tal manera que cuando veo todo el año en los filtros generales, pueda tener en un gráfico mi resumen acumulado y en otro el detalle por mes donde pueda ver siempre viendo el último mes ( desplazado hacia la derecha). Podría usar la inversión de datos, pero por lo general se visualiza de izquierda a derecha cuando queremos ver tendencia.
Semantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connection. Currently, the semantic model definition is source controlled, but these data source → connection bindings are not. After a Git sync or deployment, the connections therefore have to be mapped to the semantic model again, either manually through Semantic model settings → Gateway and cloud connections → Maps to, or programmatically using the connection binding API. The connection bindings should instead be included in the source-controlled semantic model definition and automatically applied during Git sync and deployment. Preferably, the connection ID should also support Variable Library variables. Since the connection is identified by a GUID, the binding could accept a String/GUID Variable Library value, allowing the same semantic model definition to be used across environments with different connections. The Variable Library would then provide the appropriate connection IDs for each environment. This would eliminate the need for separate manual or programmatic connection-binding steps after Git synchronization or deployment.
Bulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change the names one by one and once we press enter after changing the name, depending on your model size, it takes between 2-10 seconds to load up. If we have 10-20 columns in a table visual, we have to change the names one by one and wait for it to get loaded every single time. I suggest to include a bulk updating where we can change the names for each field used in the Visualizations Pane for any visual and click an Apply button to load up the changes in one go.
Syncing parameter of paginated report in desktop
Hi , I have the below attached filters which i need to sync and i have created parameters with creating separate data set for each parameter . The issue i am facing is while passing the parameter Metric_name in dektop with field metric_id_name then few ids are dropping . It is not passing the value and showing default All option . Metric_id_name has long text names. Metric Name is filter is working for only few ids . How can i write the parameter and query to take the exact name . or check metric id starting and see if the id is present in name . Metric_ID Metric_ID_Name MET-1509 MET-1509 - # Claims Outstanding >60 days (Receivable) MET-973 MET-973 - Compliance Risk Opinion MET-2486 MET-2486 - Outsourcing Oversight (Internal Outsourcing) MET-2488 MET-2488 - Outsourcing Oversight (Internal Outsourcing) MET-715 MET-715 - Sec Finance Income Claims Collection (>30 days) - (in millions) MET-2331 MET-2331 - PIMCO (MO) - # of impact incidents MET-1506 MET-1506 - Failed trades (for GT) MET-1037 MET-1037 - Billing Accuracy – percentage of monthly revenue - Traditional (prior prior month) MET-2603 MET-2603 - ICAMS All Incident Closure Timeliness MET-2141 MET-2141 - Failing Unit Trust and Physical Sell trades over 60 days old (Transition Settlement) Below is the Query Used on report Builder ="EVALUATE " & "VAR AsOfDate = DATE(" & Year(Parameters!SelAsOfDate.Value) & "," & Month(Parameters!SelAsOfDate.Value) & "," & Day(Parameters!SelAsOfDate.Value) & ") " & "VAR ReportedMids = CALCULATETABLE(" & "VALUES(KRI[Metric_ID]), " & "REMOVEFILTERS(KRI), " & "KRI[MetricsResults Breach Status Value] IN {""" & Join(Parameters!Breach_Status_Value.Value, """,""") & """}, " & "KRI[MetricsResults Metric Date] = AsOfDate" & ") " & "RETURN " & "SELECTCOLUMNS(" & "FILTER(" & "KRI," &"TRUE()" & IIF( UCase(Trim(Parameters!Period.Value & "")) = "3M" OR UCase(Trim(Parameters!Period.Value & "")) = "3 M", " && KRI[MetricsResults Metric Date] > EOMONTH(AsOfDate, -3) && KRI[MetricsResults Metric Date] <= AsOfDate", IIF( UCase(Trim(Parameters!Period.Value & "")) = "6M" OR UCase(Trim(Parameters!Period.Value & "")) = "6 M", " && KRI[MetricsResults Metric Date] > EOMONTH(AsOfDate, -6) && KRI[MetricsResults Metric Date] <= AsOfDate", IIF( UCase(Trim(Parameters!Period.Value & "")) = "YTD", " && KRI[MetricsResults Metric Date] >= DATE(YEAR(AsOfDate), 1, 1) && KRI[MetricsResults Metric Date] <= AsOfDate", "" ) ) )& IIF( InStr("," & Join(Parameters!Risk_unit_level1.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Risk_unit_level1.Value, ""))) = 0, "", " && (KRI[Risk_Unit_Level_1] IN {""" & Join(Parameters!Risk_unit_level1.Value, """,""") & """} || ISBLANK(KRI[Risk_Unit_Level_1]))" ) & IIF( InStr("," & Join(Parameters!Risk_Unit_level2.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Risk_Unit_level2.Value, ""))) = 0, "", " && KRI[Risk_Unit_Level_2] IN {""" & Join(Parameters!Risk_Unit_level2.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Risk_Unit_Level3.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Risk_Unit_Level3.Value, ""))) = 0, "", " && KRI[Risk_Unit_Level_3] IN {""" & Join(Parameters!Risk_Unit_Level3.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Classification.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Classification.Value, ""))) = 0, "", " && KRI[Metrics_KRI_Classification_Value] IN {""" & Join(Parameters!Classification.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!pEntityType.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!pEntityType.Value, ""))) = 0, "", " && KRI[MetricsEntity Type] IN {""" & Join(Parameters!pEntityType.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!pEntityName.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!pEntityName.Value, ""))) = 0, "", " && KRI[Metrics_Entity_ID_Name] IN {""" & Join(Parameters!pEntityName.Value, """,""") & """}" ) & IIF( Len(Code.CleanJoin(Parameters!Metric_Name.Value)) = 0, "", " && KRI[Metric_ID_Name] IN {""" & Code.CleanJoin(Parameters!Metric_Name.Value) & """}" ) & IIF( InStr("," & Join(Parameters!KRI_Result_Status.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!KRI_Result_Status.Value, ""))) = 0, "", " && KRI[MetricsResults Value Collection Status Value] IN {""" & Join(Parameters!KRI_Result_Status.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Metric_Category_Group.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Metric_Category_Group.Value, ""))) = 0, "", " && KRI[Metric Category Group] IN {""" & Join(Parameters!Metric_Category_Group.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Breach_Status_Value.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Breach_Status_Value.Value, ""))) = 0, "", " && KRI[Metric_ID] IN ReportedMids" ) & IIF( InStr("," & Join(Parameters!Region.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Region.Value, ""))) = 0, "", " && KRI[MetricsEntity_Region_Value] IN {""" & Join(Parameters!Region.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Legal_Entity_Name.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Legal_Entity_Name.Value, ""))) = 0, "", " && KRI[Legal_Entity_Name] IN {""" & Join(Parameters!Legal_Entity_Name.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!business_or_corporate.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!business_or_corporate.Value, ""))) = 0, "", " && KRI[business_or_corporate] IN {""" & Join(Parameters!business_or_corporate.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Level_2_Risk.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Level_2_Risk.Value, ""))) = 0, "", " && KRI[Level_2_Risk] IN {""" & Join(Parameters!Level_2_Risk.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Level_3_Risk_Taxonomy.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Level_3_Risk_Taxonomy.Value, ""))) = 0, "", " && KRI[Operational_Risk_Level_3] IN {""" & Join(Parameters!Level_3_Risk_Taxonomy.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Metrics_Measured_In_Value.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Metrics_Measured_In_Value.Value, ""))) = 0, "", " && KRI[Metrics_Measured_In_Value] IN {""" & Join(Parameters!Metrics_Measured_In_Value.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Metrics_Measurement_Frequency_Value.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Metrics_Measurement_Frequency_Value.Value, ""))) = 0, "", " && KRI[Metrics_Measurement_Frequency_Value] IN {""" & Join(Parameters!Metrics_Measurement_Frequency_Value.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!MetricsResults_Arrears_Value.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!MetricsResults_Arrears_Value.Value, ""))) = 0, "", " && KRI[MetricsResults_Arrears_Value] IN {""" & Join(Parameters!MetricsResults_Arrears_Value.Value, """,""") & """}" )& IIF(InStr("," & Join(Parameters!Metrics_Included_in_Report_Value.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Metrics_Included_in_Report_Value.Value, ""))) = 0, "", " && KRI[Metrics_Included_in_Report_Value] IN {""" & Join(Parameters!Metrics_Included_in_Report_Value.Value, """,""") & """}" ) & IIF( InStr("," & Join(Parameters!Metrics_KRI_Reported_To_Value.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Metrics_KRI_Reported_To_Value.Value, ""))) = 0, ""," && KRI[Metrics_KRI_Reported_To_Value] IN {""" & Join(Parameters!Metrics_KRI_Reported_To_Value.Value, """,""") & """}" )& IIF( InStr("," & Join(Parameters!Metrics_KRI_Escalated_To_Value.Value, ",") & ",", ",All,") > 0 OR Len(Trim(Join(Parameters!Metrics_KRI_Escalated_To_Value.Value, ""))) = 0, "", " && KRI[Metrics_KRI_Escalated_To_Value] IN {""" & Join(Parameters!Metrics_KRI_Escalated_To_Value.Value, """,""") & """}" ) & ")," & """MetricName"", KRI[MetricsResults_MetricName]," & """MetricDate"", KRI[MetricsResults Metric Date]," & """MetricMonthYear"", FORMAT(KRI[MetricsResults Metric Date], ""MMM YYYY"")," & """MetricMonthSort"", YEAR(KRI[MetricsResults Metric Date]) * 100 + MONTH(KRI[MetricsResults Metric Date])," & """RunDate"", KRI[RunDate]," & """Risk_Unit_L1"", KRI[Risk_Unit_Level_1]," & """Risk_Unit_L2"", KRI[Risk_Unit_Level_2]," & """Risk_Unit_L3"", KRI[Risk_Unit_Level_3]," & """Entity_Region"", KRI[MetricsEntity_Region_Value]," & """Legal_Entity"", KRI[Legal_Entity_Name]," & """Buisness_or_Corporate"", KRI[business_or_corporate]," & """Level_2_Risk"", KRI[Level_2_Risk]," & """Ops_risk_Level_3"", KRI[Operational_Risk_Level_3]," & """MetricsResults_Arrears_Value"", KRI[MetricsResults_Arrears_Value]," & """MetricsMeasuredIn_Value"", KRI[Metrics_Measured_In_Value]," & """Metrics_Measurement_Frequency"", KRI[Metrics_Measurement_Frequency_Value]," & """Metrics_Included_in ReportValue"", KRI[Metrics_Included_in_Report_Value]," & """Metrics_Included_Report_Value"", KRI[Metrics_Included_in_Report_Value]," & """Metric_KRI_Escalated_To_Value"", KRI[Metrics_KRI_Escalated_To_Value]," & """ReportedValue"", KRI[Reported_Metric_value_Formatted]," & """Metric_Entity_ID_Name"", KRI[Metrics_Entity_ID_Name]," & """Metric_Entity_Type"", KRI[MetricsEntity Type]," & """Metric_Collection_Status"", KRI[MetricsResults Value Collection Status Value]," & """Metric_Id_name"", KRI[Metric_ID_Name]," & """EntityName"", KRI[MetricsEntity Name]," & """Classification"", KRI[Metrics_KRI_Classification_Value]," & """Classification_short"", KRI[KRI_Class_Short]," & """BreachStatus"", KRI[MetricsResults Breach Status Value]," & """ThresholdAmber"", KRI[Treshold Amber]," & """ThresholdRed"", KRI[Treshold Red]," & """MetricID"", KRI[Metric_ID]," & """ReportingOrder"", KRI[Reporting_Order]," & """Action Plan"", KRI[MetricsResults Management Action]," & """Root Cause"", KRI[MetricsResults RootCause]," & """MetricCategoryGroup"", KRI[Metric Category Group]," & """ThresholdDisplay"", KRI[OPs_Thresholds_Display]" & ")"
How to Count Date Wise
Hi Team, I have data some thing like this : Date File 01/07/2026 134343434 74635577 24564675757 02/07/2026 45405645 325474699 97436487 7425742599 03/07/2026 12243434 2134 469359639 847564254 73796 04/07/2026 78874547 323435435 787546356 78567456747 05/07/2026 9808969 111232332 5666666 32323 4565636367 I need to take count of File as per Date like below : Date File 01/07/2026 3 02/07/2026 4 03/07/2026 5 04/07/2026 4 05/07/2026 5 But Power BI giving like this output : Please let me know how to get like this output : Date File 01/07/2026 3 02/07/2026 4 03/07/2026 5 04/07/2026 4 05/07/2026 5Set default x axis scrolling position
Enable selection of the default scroll position for the x-axis on a chart. For example, on a line chart with dates as the x-axis, when not all of the data can display in the view at once, the scroll defaults to the beginning/left end of the x-axis and the most recent dates are at the far end causing the end user to always have to scroll to see the most recent data. If you could set the visual to default to the right end, then the user would only have to scroll if they wanted to see more history.
Table Visual — Rounded Corners and Pill-Style Cell Backgrounds
Add the option to display cell background colors as rounded rectangles or pill-shaped labels within the native Table visual. Currently, applying a background color fills the entire cell with a solid rectangle. I would like the ability to adjust the corner radius and padding, creating a colored background around the value with space between the background and the cell edges. Suggested formatting options: Corner radius: Adjust from square corners to fully rounded pills. Padding: Control the spacing around the value and inside the cell. Background width: Fit the background to the text or use a consistent width across the column. Conditional formatting support: Apply background colors dynamically using existing rules or measures. This would be particularly useful for status values such as On Track, At Risk, and Behind, making them appear as clear, compact badges. It would improve readability and provide a more polished appearance without requiring custom visuals or SVG workarounds.Power BI August 2026 Feature Summary
Welcome to the August 2026 Power BI Feature Summary! This month includes updates across reporting, modeling, data connectivity, mobile, embedded analytics, and developer experiences, with a mix of generally available enhancements and new preview capabilities. Let's take a look at what's new. Download Power BI Desktop Events and Announcements September 15 | What a Winning Power BI Dataviz Looks Like Meet the finalists headed to Barcelona to compete for the title of Power BI Dataviz World Champion. Explore the visuals that got them there, hear their tips for creating standout dataviz, and join their virtual cheer squad before they face the ultimate challenge: 20 minutes to create a championship-winning visual live on stage. Reserve your spot. Community Conference Tickets are Getting Low The European Microsoft Fabric and SQL Community Conference take place September 28 to October 1 in Barcelona, Spain, bringing together Microsoft experts and community leaders for exclusive content, live demos, and key announcements, along with more than 130 sessions spanning Fabric, Azure AI, Databases, Power BI, and Microsoft Purview. And of course, the live Dataviz World Championships finale! The most recent event in Atlanta sold out. Don’t miss out and register for the Barcelona event with code FABCMTY200 to save €200. General Deprecation of Old File Picker experience in Power BI Desktop In April we deprecated the old file picker experience in Power BI Desktop. Starting in October, users still utilize versions of Power BI desktop from March 2026 or earlier will no longer be able to save and share Power BI files to One Drive and SharePoint. Please ensure you update Power BI desktop to keep using this functionality. Note: No action is required from users as part of this deprecation; this is simply an informational announcement. Copilot and AI Updates to required semantic model permissions for Fabric Apps Currently, users need Build permission on the underlying semantic model to view and interact with a Fabric App created with the data app template. In early September, consumers will need only Read permission on the semantic model, along with access to the Fabric app. This change supports least-privilege of access by no longer requiring the broader Build permission for app consumption. App authors will still require Build permissions on the semantic model. Learn more about creating a Fabric app connected to a semantic model. Copilot Summary and Copilot Narrative can now read visuals hidden behind bookmarks Authors commonly use report bookmarks as tabs to organize content by showing and hiding visuals on a page. In these designs, certain visuals are hidden by default and revealed only when a display-only report bookmark is triggered. Copilot previously skipped these visuals entirely, so its Summary responses reflected only part of the report. Copilot Summary can now read and consider these bookmark-revealable visuals in its responses. This covers only visuals that are hidden by default and made visible by a display-only report bookmark triggered through a bookmark button or bookmark navigator. Authors can also select these hidden visuals when configuring the Copilot Narrative visual. Visuals are read in place with no changes to the bookmark state, and RLS and OLS permissions stay fully enforced. To learn more, refer to Summarize a report with Copilot and Create a narrative visual with Copilot for Power BI. Reporting Modern visual defaults and customize themes formatting panes (Generally Available) New reports created in Power BI Desktop and the Power BI service start with the Fluent 2 base theme, giving you a polished, consistent look without formatting each visual. Use the Theme pane to set the base theme, adjust colors to your brand or pick from one of the available color palettes, change text styles, set specific visual properties, page settings, and the filter pane look and feel across your entire report, and import or export custom theme, in both Desktop or web. Figure: Customizing a report’s base theme and color palette in the Power BI Theme pane. In this release, we also removed all font overrides from the base theme, so the Text section in the Theme pane now works as intended. Change a font in one place to update titles, callouts, labels, and general text across every visual in your report, including new visuals added later. For a deeper look at what's included, see the Deep dive into Modern Visual Defaults and Customizing Theme Improvements and Deep dive into modern visual defaults and formatting your entire report blog posts. Learn more about the base themes and the Theme pane in the Visual defaults in Power BI reports documentation. Date picker for Slicer visual (Generally Available) Date pickers combine relative selections that roll forward as time passes with a calendar and slider for manual date range or single date selection. You can anchor relative options to today, the first date, or the last date in your column. Figure: Enabling single-date selection for the Date picker slicer in the Selection controls settings. New in this release, the Single date setting under Visual > Slicer settings > Selection controls restrict the slicer to one date at a time—the calendar and slider allow only a single date, and the relative options are limited to selections that return a single date. And you can now clear selections from a header icon in addition to slicer header. For more information, see the Slicer visual in Power BI documentation. Center value for donut chart (Generally Available) Donut charts can now show value in the center, no overlaid card required. Enable the center value and the donut displays it right in the middle. You control the details in the formatting pane: value format, display units, and font. Add an optional label above or below the value, place an image above or below it, or change the background filling or image of the center. Need something other than the total? Add a custom measure to the center value in the formatting pane. Figure: A donut center can show a plain total or a custom value, label, image, or background to match your report. The center value stays in sync with your data: filtering, cross-highlighting, drill-down, and selecting a slice all update it automatically. And because it lives inside the visual, it stays aligned across resizing, mobile, and dashboards, and works with screen readers. To add a center value, select your donut chart, open the formatting pane, and turn on Center value. To learn more, refer to Add a center value to a donut chart. Comments support for reports in org apps Users can now collaborate on reports in org apps using comments. Comment on report pages and visuals, start discussions with colleagues, and use ‘@mentions’ to notify others and bring them into the conversation. Comments also capture the current report context, helping others understand exactly what you're seeing when providing feedback or discussing insights. Figure: Comments pane open on a report in an org app comment box highlighted. To learn more about, see comments in Power BI reports. Matrix: Expand and collapse for column headers (Generally Available) You can now expand and collapse column headers in the matrix visual, just like you already can for row headers. When your matrix has more than one field in the Columns field well, +/- icons appear on the column headers so you can combine groups or reveal more detail directly in the visual. You can also customize the color and size of the +/- icons under Column headers > +/- icons in the format pane. Figure: Customizing the color and size of expand and collapse icons for matrix column and row headers. To learn more, see Expand and collapse row and column headers. Matrix: Set the default freeze state for row headers in the format pane Report authors can now set the default freeze state for matrix row headers directly in the format pane. Turn the Row headers toggle on or off under Layout > Freeze to control whether row headers stay visible or scroll away when consumers scroll horizontally. This default is saved with the report and applies to everyone who views it. Figure: Setting the default freeze state for matrix row headers in the Visual formatting pane. This new setting is especially useful for mobile layouts. On phones, portrait orientation limits horizontal space, so you might want to unfreeze the row headers on your mobile layout to give data values more room, while keeping them frozen on the desktop layout, which typically uses landscape orientation. Figure: Setting the default freeze state for matrix row headers in a mobile layout. The right-click Freeze row headers and Unfreeze row headers options are still available and, as before, remain transient — they apply only to the current viewing session, so consumers can flip the state temporarily without changing the report author's default. To learn more, see Freeze row headers. OneLake file URLS for report visuals and maps (Generally Available) You can now use links to image files stored in OneLake as an image source anywhere where Power BI accepts an image URL. This works in the image visual, table and matrix cells, the card visual, button and list slicers, as well as for custom icons in the Icons cell element when you use the Field value format style. OneLake file links work even though they require authentication—Power BI signs in on your behalf when the report loads, so you don't have to make images anonymously accessible to use them in your report. Copy the file URL from OneLake and paste it into any image URL field or into a column or measure set as Image URL. Example: https://onelake.dfs.fabric.microsoft.com/{workspace-id}/{item-id}/Files/{path-to-image Figure: Using a OneLake file URL as the image source for an image visual in Power BI. Reference layer maps and shape map files can also be linked from OneLake file URLs. Keep your files in OneLake and use them in your Power BI reports today! For more information, see the Display images in a table, matrix, or slicer and Image visual in Power BI documentation. Outer padding for bar, column, line, ribbon, and waterfall charts in formatting pane (Generally Available) Column, bar, clustered, line, ribbon, and waterfall charts now include an Outer padding setting under Layout, giving you control over the space between the edges of the plot area and the first and last categories. This is helpful when you want your chart to fill the visual—especially in scenarios where you've turned off the category axis and are relying on a legend, like a clustered column chart used as a comparison view. Then, you can simply resize the visual to get the look you want on your report page. Reducing outer padding on line charts with categories also lets you show more data before a scrollbar appears. Figure: Adjusting outer padding and spacing between categories to control how charts fill the plot area. To use it, select the visual and, in the Format pane, expand Columns, Bars, or Lines > Layout, then set Outer padding to 0%. To fully fill the plot area, also set Space between categories to 0%. For more information, see the Customize x-axis and y-axis properties documentation. Azure map reference layer shape-matching improvements (Generally Available) Shape matching in Azure Maps reference layers now delivers significantly better performance. When you match your Power BI data to shapes in a reference layer—for example, joining sales data to a set of custom territories or regions in a GeoJSON file—reports now render faster, and interactions like filtering, cross-highlighting, and zoom respond more smoothly. No configuration change is required; existing reports automatically benefit from the improvements. Figure: Improved Azure Maps reference layer performance, with faster rendering shown in the Performance analyzer. For more information, see the Add a reference layer to the Azure Maps Power BI visual documentation. Azure map loads filtered selection and autozoom (Generally Available) The Azure Map visual has a 30,000 data point rendering limit, and previously, points beyond that limit didn't display—even when you filtered the report to focus on a smaller area whose data hadn't originally loaded. Now, when you filter to a smaller selection, the visual reloads to include the newly relevant data points that weren't part of the original 30,000. This means you can start with a broad view of your data and drill into any subset—by region, category, time period, or through cross-filtering—and be confident the map shows the complete picture for what you've filtered to, not just what fit in the initial load. Figure: Filtering the report to Washington reloads the relevant ZIP code shapes and automatically zooms the Azure Maps visual to the selected area. The Azure Map visual also now automatically zooms to fit the currently filtered area. When you or a report viewer applies filters, use slicers, or cross-filter from another visual, the map reframes to the extent of the visible data instead of staying at the original viewport. This keeps the map focused on the data being analyzed and removes the need to manually pan and zoom after every filter change. For more information on Azure Map, see the Azure Maps visual for Power BI documentation. Slicer visual dropdown border color, open icon, and hierarchy expand and collapse icon colors in formatting pane (Generally Available) Based on your feedback, we’ve added more slicer formatting options beyond the selection icon, giving you greater control over the slicer’s appearance. When you add more than one field to the slicer to have a hierarchy in vertical list or dropdown style, make sure the icon color matches your report. And dropdown style, offering a compact slicer to your report has more formatting options. Figure: Customizing the slicer dropdown border, open icon, and accent bar in the Visual formatting pane. The new top-level Dropdown section in the Visual formatting pane lets you customize the dropdown box in both its open and closed states, including border color (with conditional formatting), rounded corners, and the open icon color (with conditional formatting) and transparency. A new Accent bar option adds a color bar to the dropdown box with settings for color (with conditional formatting), position, transparency, and width. For hierarchy slicers, the top-level Hierarchy section lets you color the expand and collapse icons (with conditional formatting) and choose which icon to use. For more information, see the Slicer visual in Power BI documentation. Modeling More control over Semantic Model refresh in Power BI Service We've added new refresh options in Power BI Service to give you greater control over how semantic models are refreshed. Previously, selecting Refresh always performed a schema sync followed by a data refresh. While this works well in most scenarios, there are times when you may want to refresh data without updating the model schema or vice versa. For example, in Direct Lake semantic models, a Lakehouse table might have changed by adding new columns, but you may want to load the latest data without bringing those schema changes into the model. Figure: New model refresh options in Power BI Service Model view. The Refresh button now includes three options: Refresh schema and data: Updates the schema and then refreshes data. Sync schema only: Applies schema changes from the data source, such as new columns or data type changes. Refresh data only: Loads the latest data while preserving the current semantic model schema. In addition, refresh operations can now be performed at the table level. This allows you to refresh a specific table instead of the entire semantic model and choose whether to refresh its schema, data, or both. Figure: New table refresh options in Power BI Service Model explorer. These enhancements provide more flexibility and control over semantic model maintenance, helping you refresh exactly what you need while minimizing unnecessary changes and processing. Refer to the Data refresh in Power BI documentation for more information. Convert Direct Lake Tables to Import Storage Mode in Web Modeling (Preview) Direct Lake on OneLake supports composite models by allowing for mixing Direct Lake tables with Import and DirectQuery tables. You can now convert individual Direct Lake tables to Import storage mode directly in Power BI web modeling, giving you a seamless way to build a Direct Lake composite (mixed mode) semantic model. Open a Direct Lake on OneLake semantic model in web modeling, select one or multiple tables, and change the Storage mode from Direct Lake to Import in the Properties pane. The modeling flow guides you through configuring a connection and refreshing the table into Import mode. Because Direct Lake and Import tables support regular relationships, performance remains unchanged. Figure: Change the Storage mode property from Direct Lake to Import to convert a single table. A warning dialog will be surfaced before continuing. This feature will be rolling out over the next few weeks. Refer to the Direct Lake in web modeling documentation for more information. Direct Lake Calculated Columns (Preview) You can define calculated columns directly in your semantic model using DAX in web modeling and Power BI Desktop, without changing the table storage mode or modifying data upstream. Key behaviors Only the User Context expression context is supported. User-context-aware DAX functions such as USERCULTURE() are supported. Columns do not materialize and are evaluated at query time. Security context is respected (RLS and OLS). Columns cannot be used in relationships because they do not materialize. Expressions that do not reference user-aware functions or secured columns behave like any other DAX calculated column. Figure: Creating a concatenated location field. Figure: Month names displayed using USERCULTURE(). "Customer Location" returns the same value for every user unless the security context differs. "Month Name" adapts to the language of the person viewing the report. Figure: Month names are localized based on the user's culture using USERCULTURE(). No preview switch is required - open a Direct Lake on OneLake semantic model in the web or edit in Desktop, add a calculated column, and start authoring in DAX. To learn more, see the Create calculated columns in Power BI Desktop documentation. Data connectivity Accessibility, Dark Mode, and Usability Upgrades Theming improvements for better accessibility In this release, we’ve invested in a range of theming improvements that address color contrast and readability across both the light and dark themes. Users who rely on higher-contrast visuals will notice cleaner, more legible interface elements throughout the Power Query UI. Highlights: Improved color contrast across interface elements in both light and dark themes. More consistent theming that keeps controls, text, and icons clearly distinguishable. A stronger foundation for accessibility that benefits all users, regardless of theme preference. Figure: Better contrast for connectors and white background for icons. Better contrast for connector icons in Dark Mode Connector icons are how you quickly recognize your data sources, but in Dark Mode, icons with transparent backgrounds could blend into the surrounding UI and become hard to identify. We’ve fixed that. Now, when a connector icon has a transparent background, it automatically receives a white background in Dark Mode. The result: connector icons stand out clearly and stay easy to identify across the new Power Query UI, making it faster to find and select the right data source briefly. To learn more, refer to the Get data in Power BI Desktop documentation. Mobile Rotate view in the mobile report footer The Rotate view button is now available in the Power BI Mobile report footer, letting you switch layouts with one tap for larger visuals and a wider view—even when your phone is locked in portrait orientation. This is especially helpful for reports that don't have a mobile-optimized layout, which open in portrait by default. Just tap Rotate view to get a wider, more readable view, then tap again to switch back. This feature is rolling out soon to Power BI Mobile for iOS and Android - stay tuned! Figure: Tapping Rotate view in the report footer to get a larger view of the report. To learn more about the actions in the report footer, refer to the Explore reports in the Power BI mobile apps documentation. To learn how to build a mobile-optimized layout for your reports, see the mobile layout documentation. Export data to Excel in the Power BI mobile app Export data from Power BI report visuals directly from your phone or tablet. With Export data now available in the Power BI mobile app for iOS and Android, you can quickly take the data behind a visual into Excel for further analysis or sharing, without switching to the Power BI service on another device. To export, open a report visual in focus mode or open the visual’s More options (…) menu, and select Export data. The export starts automatically using the supported Excel format for that visual. The exported data reflects your current filters, slicers, drill state, permissions, and row-level security. When the file is ready, use your device’s sharing options to open, save, or share it. Figure: Exporting data from a report visual to Excel in the Power BI mobile app, via focus mode or open the visual’s More options (…) menu. To learn more, see Export data from a Power BI visualization. Embedded Analytics Enhancements to Power BI Embedding in SharePoint Online Embedding Power BI reports and report pages in SharePoint Online is now easier. With our new UI, you now have the option to directly select the workspace you want to embed in SharePoint, rather than copying and pasting the full URL. Simply navigate to SharePoint online, add Power BI content, and the new menu will allow you to browse workspaces and reports you have access to. Alongside embedding reports and report pages, you can now also embed a visual. Simply select the "Embed a single visual" toggle to select the specific visual you want to embed. Figure: Embedding a Power BI visual with the new SharePoint Online Experience. More details about these enhancements can be found in the Power BI and SharePoint Documentation. Developers + API’s Faster PBIP development with instant reloads and VS Code integration A faster PBIP editing experience is here. If you're working with Power BI Projects (PBIP), you can now edit project files outside Power BI Desktop and reload those changes instantly, without restarting the application. Power BI Desktop automatically detects changes made to your files and prompts you to apply them with a single click. Figure: Apply external changes prompt in Power BI Desktop. To make editing even easier, we've also added a built-in entry point that opens your project directly in Visual Studio Code. Figure: Open Visual Studio Code entry point in Power BI Desktop. Whether you're making edits in VS Code or using external tools to update your project files, you can now move seamlessly between your tools and Power BI Desktop without breaking your flow. Learn more Third party custom visuals Need more visual options for your report? Power BI reports support custom visuals built to fit your exact needs. Browse hundreds of options in AppSource, also available directly from Power BI Desktop, or develop your own and add it to a single report, share it across your organization, or publish it to AppSource for the community. You can even develop a custom visual tailored to your specific requirements with AI coding tools like GitHub Copilot Free. The following are some updates from the community-based custom visuals you can use in your reports today. PowerGantt Chart by Nova Silva The PowerGantt Chart helps teams plan, track, and communicate project timelines directly in Power BI. This month's update is shaped by your feedback, and we're grateful to the community of users whose suggestions keep guiding how the visual evolves. We've added three enhancements that give you finer control over how schedules and baselines are displayed. What's New? Baseline customization – Set the baseline bar size relative to the actual task bar and move milestone icons onto the baseline so planned versus actual delivery is easy to compare. Squared bar edges – Choose squared edges on item bars for a cleaner, more technical look. Vertical grouping – Group tasks vertically to organize large project structures by phase, team, or workstream. Whether you're managing product launches, construction schedules, or multi-team programs, these refinements make complex timelines easier to read briefly. Project managers, PMOs, and analysts gain sharper baseline comparisons, cleaner layouts, and better navigation across busy projects. Try the PowerGantt Chart for FREE now on your own project data by downloading it from the AppSource. Questions or remarks? Visit us at: NovaSilva. Slicer Panel by Powerviz Powerviz Slicer Panel is an advanced, all-in-one slicer that combines lists, dropdowns, sliders, buttons, date pickers, switches, and text slicers in one panel. With built-in templates, full customization, and import/export, it makes filtering smarter, simpler, and more interactive. Key Features Multiple Slicers in One Build: Bring together a wide variety of slicer types, including dropdown, expanded list, date, button, text, slider, and switch slicers, all within a single, unified panel, to filter your entire report from one place. Display Mode: Switch between Canvas, Pop-up, and Pop-up by Slicer. Orientation & Position: Arrange slicers and dock the panel top, bottom, left, or right. Panel Header: Show slicer icon, text, applied count, search, clear, and saved slicers. Slicer Action Icons: Edit, expand/collapse, sort, clear, rank, duplicate, or delete each slicer. Add Tabs: Group slicers into tabs for organized filtering. Saved Slicer: Store filter selections as reusable states. Conditional Formatting: Style slicer values with rule-based formatting. Advanced Search: Search across slicers and fields instantly. Other features included Templates, Import/ Export Themes, Search within Slicer, Ranking, Sorting, and more. Try Slicer Panel visual for FREE from App Source Check out all features of the visual Step-by-step instructions YouTube Video Learn more about visuals Follow Powerviz on LinkedIn Figure: From multiple slicer types to display modes, orientation, and saved slicers, every feature is designed to make your filtering more flexible, interactive, and effortless. Drill Down Map PRO by ZoomCharts When visualizing data with geographic coordinates, what better way to do it than literally placing it on a map? That’s why map charts are a growingly popular visualization type in Power BI reports, and the Drill Down Map PRO custom visual by ZoomCharts expands on the capabilities of map charts. Node Clustering: Multiple nearby nodes can create clusters and even display the values as pie charts. Simply zoom in to drill down. Base Layer Customization: Choose between AzureMaps or any custom tileserver, use your own images as the base layer, or disable it entirely. Custom Shape Layers: Enable up to 10 individually customizable shape layers. Use preset shapes or import your own KML/GeoJSON files. Conditional Formatting: Automatically apply color fill to each area by comparing their values against other shapes or by using each shape’s own reference value. And More: Paginated tooltips, custom tooltip fields, auras, node images, lasso tool. Figure: Reveal deeper insights with clustering, pie charts, custom shape layers, and flexible base map options tailored to your reporting needs. Figure: Customize every aspect of your map with conditional formatting, node images, auras, advanced tooltips, and intuitive selection tools. Drill Down Map PRO works incredibly well with other visuals by dynamically cross-filtering data, enabling you to build even more insightful and user-friendly Power BI reports. Get Drill Down Map PRO on AppSource Closing That's a wrap for the August 2026 Power BI Feature Summary. This month's release includes improvements across reporting, modeling, data connectivity, mobile experiences, embedded analytics, and developer workflows, along with continued investments in Copilot, accessibility, and Direct Lake capabilities. We hope these updates help you build, manage, and share data experiences more effectively. As always, we appreciate your feedback and look forward to hearing how you're using these features in your organization.
