Hi there,   Visual calculations are improving, but they would be even better if we were able to use parameters with them. For example, the MOVINGAVERAGE() function requires a constant as its windowSize. Users ask us to be able to change the window dynamically on the visuals ... View more

Today if you have a calculation item with in a calculation group you want to reuse as a part of another calculation, you have to rewrite that code in a var in the new calculation item.  It would be great to be able to just reference the other calculation item within the calc group to limit doubling of code and limit possiblity of errors when coding.   ... View more

There is currently no way to retrieve correct totals for the table dataviewmapping when datareductionalgorithm is used. The returned total is of the loaded data. This has been confirmed to me by the Custom Visuals team. Quoting the response I received today: "Answering your question — no, there isn’t any undocumented or hidden method to display totals for the entire dataset when using paginated data in a table layout. The built-in Power BI Table visual calculates totals internally through the host’s DAX engine, which isn’t accessible to custom visuals. At the moment, these are no special workarounds, the possible options would be: Providing a pre-aggregated total from your data model (for example, via a DAX measure or calculated table) and pass it to the visual as a separate field. Using a non-paginated dataView for smaller datasets where you can safely compute totals within the visual itself." This prevents building certain visuals like true table visuals. ... View more

Allow the rotating of column headers in tables and matrix at a 90 degree angle ... View more

A design limitation in the current Git Integration REST API implementation that prevents Service Principal authentication from performing specific Data Warehouse operations (Ex , Update). As seen internally using the Request ID generated : “Exception object created: Microsoft.PowerBI.ArtifactRegistry.PowerBIArtifactTypeNotFoundException: The following artifact types are not found in the artifact registry: [SynapseNotebook, dataset]”   The public guide showing Update API using Service Principle is supported, while its not      This will help to perform end to end automation with API. ... View more

I want to remove the option for "Members" to manually add users to the workspace, so they are required to do it through the AD groups designated by the administrator. ... View more

Dear all,   the overview is great. is it also possible to add the relation ID and name so that we know who's the client behind (non-CID data)? @EMEAWeekly2.0   thank you,   Best, Elsa   ... View more

In Power BI, there is no option to apply a standard formatting setup (background, visuals, colors, and fonts) across all report pages. Currently, if I format one page, I have to manually repeat the same formatting on every other page, which is time-consuming and prone to inconsistencies. There should be a feature to set default formatting that automatically applies to all pages, while still allowing customization for specific visuals or pages when needed. ... View more

Currently, Power BI’s Python integration is only supported in desktop environments and personal gateways, which limits its use in enterprise settings where scheduled refreshes must run through the Enterprise Gateway. This restriction prevents teams from leveraging Python for advanced data transformation, statistical analysis, and custom visualizations within governed, refreshable Power BI datasets.   Enabling Python execution through the Enterprise Gateway would: - Allow secure and automated refreshes of Python-powered dataflows and reports. - Remove the need for local Python installations or manual refreshes. - Enhance Power BI’s analytics capabilities by integrating modern data science workflows. - Improve consistency between development (Power BI Desktop) and production (Service) environments.   This feature would make Power BI more suitable for organizations that rely on Python-based ETL, data science, or machine learning preprocessing steps, without compromising governance or scalability. ... View more

Currently, OTR Team only see FPD past due and FPD>RSD, and this is very helpful.   However, it would also be great for OTR Team to see FPD<1 week to be able to monitor the expected shiptments from plant before they enter the past due date. Similar with monitoring CTD<1week to prevent CTD past due. ... View more

Currently, there doesn't seem to be a way to reference item() separately when Filter is within ForEach. In my example, I use Filter within my ForEach to filter down a table that from a previous LookUp activity. The idea is to get a record from LookUp (using Filter) to match the current item() of ForEach loop. The issue is when defining the expression for Filter, I'd use "@equal(FilterItem, ForEachItem)" and that can't be done since there's no clear distinction for "item()" in this scenario. Hope this gets improved soon. It may be a minor but large improvement for data pipelines.  ... View more

I would really like Query Folding for Data Lake/File System/Blob data sources. I have Azure Data Factory jobs create daily or hourly data. But to get it into PowerBI I need another job to wrap up multiple days worth of data into one text file that's then copied into Power BI daily. If it's 30 days worth of data, that means that Power BI is re-copying 29 days worth of data. But if there was Query Folding, Power BI could drop just 1 days worth of data and copy in 1 days worth of data. ... View more

Pipelines are really handy low-code ways to manage file movement, but the lack of a true Move option in a Copy activity makes pipelines incredibly CU-heavy when it comes to large numbers of files. This is due to Copy...well...copying files rather than using Microsoft's file system APIs to change metadata like you can do in Fabric notebooks with utilities.   Please add a Move option that doesn't duplicate files but instead changes their metadata so files don't have to literally be duplicated. ... View more

Currently, when we generate a usage report in Power BI, we can view and analyze it within that report, but we can’t access or reuse the underlying dataset. It would be extremely useful if Power BI provided an option to connect to or reuse the dataset behind usage reports. This would allow users to integrate usage metrics (like number of viewers, report frequency, or activity trends) into their own dashboards and combine them with other organizational data. Use Case: For example, I’ve created a usage report for monitoring report access. I’d like to use that same dataset in another report to track engagement across multiple workspaces but currently, the usage data is not available as a reusable dataset. Adding this feature would make it much easier to analyze report adoption, monitor usage trends, and automate governance reporting within Power BI. ... View more

---------- Message ---------- Failed to execute 'ariaNotify' on 'Document': Failed to read the 'priority' property from 'AriaNotificationOptions': The provided value 'none' is not a valid enum value of type AriaNotifyPriority. ---------- Pile ---------- React.useCallback(()@webpack://node_modules/@fluentui/react-aria/lib/AriaLiveAnnouncer/useAriaNotifyAnnounce.js:21:23 announce()@webpack://@powerquery/monolith-ui/ClientShared/Scripts/Components/Dialog/DialogRenderer.tsx:33:45 ---------- ID de session ---------- 7a0206f0-5582-48e6-ab4c-5adcb1e33c77 ---------- Script Mashup ---------- [DefaultOutputDestinationSettings = [DestinationDefinition = [Kind = "Reference", QueryName = "DefaultDestination", IsNewTarget = true], UpdateMethod = [Kind = "Append"], DestinationTypeSettings = [Kind = "Table"]], StagingDefinition = [Kind = "FastCopy"]] section Section1; shared DefaultDestination = Fabric.Warehouse([CreateNavigationProperties = false]){[workspaceId = "a848bdde-71f0-49ec-b240-6e06f0a722ef"]}[Data]{[warehouseId = "8de00ccf-30b3-4684-86b5-40e8f47cf812"]}[Data]; [BindToDefaultDestination = true] shared dim_client = let Source = AzureStorage.DataLake("https://massarfabric.dfs.core.windows.net/"), #"Lignes filtrées" = Table.SelectRows(Source, each Text.Contains([Name], "wwi.dimension_Customer.txt")), Navigation = #"Lignes filtrées"{[#"Folder Path" = "https://massarfabric.dfs.core.windows.net/sampledata/", Name = "wwi.dimension_Customer.txt"]}[Content], #"CSV importé" = Csv.Document(Navigation, [Delimiter = ",", Columns = 11, Encoding = 65001, QuoteStyle = QuoteStyle.None]), #"En-têtes promus" = Table.PromoteHeaders(#"CSV importé", [PromoteAllScalars = true]), #"Type de colonne changé" = Table.TransformColumnTypes(#"En-têtes promus", {{"Customer Key", Int64.Type}, {"WWI Customer ID", Int64.Type}, {"Customer", type text}, {"Bill To Customer", type text}, {"Category", type text}, {"Buying Group", type text}, {"Primary Contact", type text}, {"Postal Code", Int64.Type}, {"Valid From", type datetime}, {"Valid To", type datetime}, {"Lineage Key", Int64.Type}}, "fr"), #"Lignes vides supprimées" = Table.SelectRows(#"Type de colonne changé", each not List.IsEmpty(List.RemoveMatchingItems(Record.FieldValues(_), {"", null}))), #"Premières lignes supprimées" = Table.Skip(#"Lignes vides supprimées", 1) in #"Premières lignes supprimées"; [BindToDefaultDestination = true] shared nouveaux_client = let Source = AzureStorage.DataLake("https://massarfabric.dfs.core.windows.net/"), #"Lignes filtrées" = Table.SelectRows(Source, each Text.Contains([Name], "wwi.nouveaux_clients.txt")), Navigation = #"Lignes filtrées"{[#"Folder Path" = "https://massarfabric.dfs.core.windows.net/sampledata/", Name = "wwi.nouveaux_clients.txt"]}[Content], #"CSV importé" = Csv.Document(Navigation, [Delimiter = ",", Columns = 11, Encoding = 65001, QuoteStyle = QuoteStyle.None]), #"En-têtes promus" = Table.PromoteHeaders(#"CSV importé", [PromoteAllScalars = true]), #"Type de colonne changé" = Table.TransformColumnTypes(#"En-têtes promus", {{"Customer Key", Int64.Type}, {"WWI Customer ID", Int64.Type}, {"Customer", type text}, {"Bill To Customer", type text}, {"Category", type text}, {"Buying Group", type text}, {"Primary Contact", type text}, {"Postal Code", Int64.Type}, {"Valid From", type datetime}, {"Valid To", type datetime}, {"Lineage Key", Int64.Type}}, "fr"), #"Lignes vides supprimées" = Table.SelectRows(#"Type de colonne changé", each not List.IsEmpty(List.RemoveMatchingItems(Record.FieldValues(_), {"", null}))), #"Premières lignes supprimées" = Table.Skip(#"Lignes vides supprimées", 1) in #"Premières lignes supprimées"; [StagingDefinition = [Kind = "FastCopy", Required = true], DataDestinations = {[Definition = [Kind = "Reference", QueryName = "dim_customer_DataDestination", IsNewTarget = true], Settings = [Kind = "Manual", AllowCreation = true, ColumnSettings = [Mappings = {[SourceColumnName = "Customer Key", DestinationColumnName = "Customer Key"], [SourceColumnName = "WWI Customer ID", DestinationColumnName = "WWI Customer ID"], [SourceColumnName = "Customer", DestinationColumnName = "Customer"], [SourceColumnName = "Bill To Customer", DestinationColumnName = "Bill To Customer"], [SourceColumnName = "Category", DestinationColumnName = "Category"], [SourceColumnName = "Buying Group", DestinationColumnName = "Buying Group"], [SourceColumnName = "Primary Contact", DestinationColumnName = "Primary Contact"], [SourceColumnName = "Postal Code", DestinationColumnName = "Postal Code"], [SourceColumnName = "Valid From", DestinationColumnName = "Valid From"], [SourceColumnName = "Valid To", DestinationColumnName = "Valid To"], [SourceColumnName = "Lineage Key", DestinationColumnName = "Lineage Key"]}], DynamicSchema = false, UpdateMethod = [Kind = "Replace"], TypeSettings = [Kind = "Table"]]]}] shared dim_customer = let Source = Table.Combine({dim_client, nouveaux_client}), #"Type de colonne changé" = Table.TransformColumnTypes(Source, {{"Postal Code", Int64.Type}, {"Valid From", type datetime}, {"Valid To", type datetime}}) in #"Type de colonne changé"; shared dim_customer_DataDestination = let Pattern = Fabric.Warehouse([HierarchicalNavigation = null, CreateNavigationProperties = false]), Navigation_1 = Pattern{[workspaceId = "a848bdde-71f0-49ec-b240-6e06f0a722ef"]}[Data], Navigation_2 = Navigation_1{[warehouseId = "8de00ccf-30b3-4684-86b5-40e8f47cf812"]}[Data], TableNavigation = Navigation_2{[Item = "dim_customer", Schema = "dbo"]}?[Data]? in TableNavigation; ... View more

In the Fabric or data factory, for a given DataFlow - Gen1/Gen2, there should be an option to schedule the refresh MONTHLY once of the model. Right now its weekly or daily.  If the underlying data doesnt change on monthly basis and the requirement is by monthly, we can save the capacity utilization for reports from customer end.  ... View more

In the power BI service, for a given Semantic Model, there should be an monthly option to schedule the refresh of the model. Right now its weekly or daily.  If the underlying data doesnt change on monthly basis and the requirement is by monthly, we can save the capacity utilization for reports from customer end.  ... View more

I've seen this in custom map visuals, but it would be great to be able to use images as bubbles in the native Azure Maps visual. For example, if I'm plotting different retailers on a map I would be able to use their logos instead of colors to distinguish them.  ... View more

When building financial statements such as Profit & Loss reports in Power BI, it would be much easier and cleaner if the Matrix visual supported displaying hierarchy items below their children when expanded. Currently, while it’s possible to place subtotals below, this approach replaces the hierarchy label with a generic “Total” label. As a result, key financial terms (e.g., Gross Profit, Operating Income, Net Income) are displayed above their related items instead of below, which does not match standard financial reporting layouts.   Proposed improvement: Add an option in the Matrix visual to position parent (subtotal) items below their children, while retaining the original hierarchy label instead of the generic “Total.”   Benefits: Enables creation of properly formatted Profit & Loss and other financial statements without workarounds. Improves readability and alignment with standard accounting presentation formats. Reduces the need for complex DAX or custom visuals just to achieve correct subtotal placement. ... View more