Nos visuais de barras, um novo campo para permitir informar uma medida para acompanhar o progresso, atingimento ou evolução referente ao valor informado no eixo X.   Exemplo: ... View more

Poderia implementar no visuais de barras e colunas dos visuais do power bi, a configuração de selecionar qual a forma das barras ou colunas, além da largura existente, poder também informar o tipo, por exemplo cantos arredondados e especificar o tamanho que deseja em px. Acredito que isso enriquecerá ainda mais a forma de visualização dos visuais que barras ou colunas para demonstrar valores. Obrigado pela atenção. ... View more

The input slicer (formerly called text slicer) does not accept multi line input, as in no carriage returns, line feeds, new lines, etc.    While it does accept multiple inputs this is not the same as multi-line input.    The issue is if you want to add commentary (via translytical task flows) that goes across multiple lines (e.g. more detailed commentary such as end of month discussions), you are unable to do this in a way that is displayed over multiple lines (instead it just becomes a single wall of text).   This also means that if you wanted to enter commentary using markdown syntax this is also not possible (as markdown syntax requires new lines).  ... View more

When exporting to PDF - I will select the "Current Values" option in the popup as well as select "Only export current page". There were no prior issues with this feature, but now it seems to remove filtering when executing.  ... View more

Please make the Page Preview image in the email larger so that users can consume directly from the email.  This would be soooo useful! ... View more

Problem: In S3NS, all API and authentication calls must use custom sovereign endpoints . However, there is no option in Power BI Desktop or the Gateway to override or configure these endpoints.   Ask: Enable support in Power BI Desktop and Data Gateway to configure or override default BigQuery endpoints, allowing connections to sovereign environments like S3NS. Benefit: This would unblock users operating in sovereign cloud environments and ensure compatibility with region-specific security and compliance requirements. ... View more

Hello, Source Control integration for Power BI (Fabric) is a great feature, but it does not support all the items. Especially, Activator Alerts cannot be committed. Would it be therefore possible to extend Source Control feature with: -> having the possibility to define .gitignore -> start supporting Activator Alerts for Source Control many thanks in advance ... View more

We don't currently use Fabric Copilot because of the CU risk or our Fabric capacity, and as a result have it turned off on our tenant.   Power BI report builders and consumers in my organization resort to copying and pasting code and issues to M365 Copilot for help, which requires additional time and loses context of the object you are working on, and is not agentic. We are losing productivity gains and potentially better results.    Pro code developers are starting to use GitHub Copilot in VS Code but this is not accessible for everyone.   I can see that the Fabric and Power BI Copilot features released to date and data agents would be beneficial for both types of users, however due to the cost it will remain turned off for the foreseeable future unless the costing changes or we can bring our own user licence for AI features.   Most of the Power BI builders/developers in my org have a M365 Copilot or GitHub Copilot licence, I happen to have both at the moment. It seems strange that we can't use these Microsoft licences that we already pay for to use Copilot in Fabric and Power BI. Can we please have the ability to bring our own user AI licences.   The uptake of Fabric copilot features will increase and we will require more user licences as a result. GitHub Copilot and M365 Copilot also have better governance features for organization admins to track queries and usage. ... View more

Currently, when using the Edit interactions option in Power BI, the interaction buttons, such as filter, no filter, and highlight, appear as small icons near the upper edge of each visual. In reports with many elements, cards, charts placed close together, or overlapping visuals, these buttons can often become hidden behind other objects or very difficult to click, even when zooming in significantly. This makes it harder to configure interactions, especially on dense report pages or more complex layouts. The suggestion is that, when Edit interactions is enabled, Power BI could display a semi-transparent overlay over each visual, while still keeping the visual content visible in the background. Inside this overlay, the interaction buttons could be shown centered within the visual, with a larger size and better spacing. Suggested behavior: Apply a semi-transparent overlay over each visual; Display the Filter, No filter, and Highlight buttons centered within the visual; Increase the clickable area of each button; Prevent the buttons from being hidden behind other visuals; Improve usability on pages with many cards, charts, and overlapping elements. This improvement would make the process of editing visual interactions clearer, more accessible, and more productive, especially for reports with complex layouts. Actual:     Check out a prototype below:     ... View more

When viewing the Output window for a pipeline run, the UI currently focuses heavily on individual activity status. To find the total time the entire pipeline took to complete, users often have to navigate back to the Monitoring hub or the Run History list. I suggest displaying the (Total) Pipeline Duration prominently at the top of the Output window alongwith Pipeline run ID and Pipeline status.     ... View more

Many Power BI users, especially beginners and business users, build dashboards by dragging and dropping visuals without a clear understanding of which chart type is most appropriate for their data. This often leads to ineffective dashboards that fail to communicate insights clearly.   I suggest introducing an AI-powered feature within Copilot that can analyze the dataset and recommend the most suitable visualizations based on data structure, relationships, and the intended analytical goal. For example, when a user selects fields, Copilot could suggest whether a bar chart, line chart, KPI, or other visual would best represent the data, along with a brief explanation.   This feature would significantly improve dashboard quality, reduce the learning curve for new users, and promote better data storytelling practices. It would be especially valuable for students, non-technical users, and professionals transitioning into data analytics, helping them build more meaningful and insight-driven reports rather than relying on trial-and-error. ... View more

Power BI allows changing the color of apps, but the current palette is very limited. Adding more subtle, pastel, and neutral color options would greatly improve usability and visual comfort. Please give me a nicer pink.... I hate the salmon color. ... View more

Currently call the endpoint refreshes the entire endpoint. Please allow the ability to refresh single-tables or sets of tables. This will reduce wait times when only needing a subset of tables refreshed using the endpint. Thank you. ... View more

A user is unable to select Analyze in Excel from a report within an app in the Power BI service. The user has been granted Viewer access to the workspace, and the customer does not want to provide Build permission on the semantic model to end users. The user understands that this behavior is expected under the current permission setup and would like to know if there are any available workarounds for this limitation.   ... View more

A full circle gauge visual would be a great feature to add and will remove reliance on custom visuals (see attached) to achieve the desired chart. A simple change to the current Gauge visual to allow customisation of the shape i.e semi circle or full circle would work to avoid cluttering the exisitng build panel.   It would also be great to have the option to build a data label and sub label into the centre of the gauge as shown below. ... View more

Category color in the new Card visual resets when repointing to a different data source. Even when using the same field, changing the data source causes the category/header color to revert to default. This breaks formatting consistency and requires manual rework during dataset switching (e.g., Dev → Prod). Formatting should persist when the same field is used. ... View more

Is it possible to have on different PowerBi views to have a small star och pin, in order to choose 5 favourites - to have easy access to most used views in PowerBI? Thanks! ... View more

Power BI Service can make custom visuals appear blurry when the report page is displayed at a scaled zoom level, for example 87%. This happens because Power BI Service applies a CSS transform scale to the report container. As a result, the whole visual iframe is scaled like a bitmap, causing blur. The same visual is sharp in Power BI Desktop and at 100% zoom in the Service. It would be very useful if Power BI exposed the current page scale, for example pageScale, inside VisualUpdateOptions, so custom visuals could adjust their rendering correctly. Alternatively, Power BI Service could manage page zoom using a more rendering-friendly approach, such as SVG viewBox/layout resizing instead of external CSS scaling. This would help custom visuals, especially canvas/SVG/HTML visuals, remain sharp at all page zoom levels. ... View more

I would like to suggest a feature that allows slicers to remain visible (fixed or “sticky”) while scrolling through a report page in Power BI. Currently, when report pages are extended vertically, slicers scroll out of view. This makes it difficult for users to adjust filters without scrolling back to the top or relying on duplicated slicers or bookmarks as workarounds. Proposed Functionality: Introduce an option to “freeze” or “pin” slicers (or any visual) so they remain visible on screen while the rest of the report scrolls. This could work similarly to: Sticky headers in web design Freeze panes in Excel Suggested Options: Toggle setting: “Stay visible while scrolling” Ability to pin visuals to top or side of the canvas Compatibility with existing slicer sync functionality Benefits: Improves usability for long, scrollable reports Reduces need for duplicated slicers or complex bookmark setups Enhances user experience, especially for dashboards with many visuals Use Case: In reports with multiple visuals arranged vertically, users often need to change slicer selections while reviewing content further down the page. A sticky slicer would allow continuous interaction without interrupting the workflow. Conclusion: This feature would significantly improve navigation and interactivity in Power BI reports and align with common UX patterns seen in other tools. Thank you for considering this suggestion! ... View more