Exported PDF from PowerBI to not have any indents/borders
Currently, using the "Export to PDF" option in PowerBI results in two consistently buggy results: A white border/indent is generated, increasing the size of the page from 8.5x11 to 9x11.5 Sometimes shrinking the contents of the page within that same changed-size letter page. Screenshots below. It seems like this is a known issue with PowerBI, but not sure I have seen anything suggesting it will be fixed anytime soon. At least if the option to print was offered, we could configure a print to PDF setting that would remove these issues.
Comments field for Power BI Gateways
It would be helpful to have a dedicated Comments field for Power BI Gateways. This would allow administrators to add notes or relevant information about a specific gateway such as its purpose, maintenance notes, special configurations etc. Having a comments field would improve gateway management, documentation and knowledge sharing across teams especially in environments with multiple gateways.
Support Native SQL LIKE / NOT LIKE Wildcard Filtering Across Power BI Reports
Description Currently, Power BI does not provide a native way for report consumers to perform dynamic SQL-style wildcard filtering using patterns such as LIKE '____' - Above return all values with exactly four characters LIKE '__A_' - Return all four-character values where the third character is "A" Many enterprise reporting scenarios require users to enter dynamic search patterns similar to SQL LIKE and NOT LIKE functionality. While workarounds using DAX, calculated columns, custom visuals, or custom logic may be possible for individual fields, these approaches are not scalable when reports contain hundreds of filterable columns. Current Limitation After engagement with Microsoft Support, Advisory, and Architecture teams (Case #2606220040001996), it was confirmed that: Power BI currently has no native runtime implementation of SQL LIKE / NOT LIKE filtering. Existing alternatives do not adequately support large-scale implementations with hundreds of columns. Third-party visuals such as Smart Filter do not fully support SQL-style wildcard matching (for example _ as a single-character wildcard). This has been identified as a current product limitation. Suggested Enhancement Provide native filtering capabilities that support standard SQL wildcard expressions within Power BI report filters and slicers, including: % for multi-character matching _ for single-character matching LIKE and NOT LIKE style filtering behavior User-entered runtime pattern matching Consistent functionality across all text columns without requiring custom DAX or calculated columns Example Scenarios User Input Expected Result ____ Return all values with exactly 4 characters __A_ Return all 4-character values where the third character is A %ABC% Return values containing ABC A% Return values starting with A %XYZ Return values ending with XYZ Business Impact This enhancement would provide significant value for organizations with large-scale enterprise reporting environments by: Reducing reliance on custom DAX and calculated columns Improving report usability for business users familiar with SQL-style searches Enabling dynamic filtering across hundreds of columns without additional development effort Improving scalability, maintainability, and performance of enterprise Power BI solutions Supporting Information Microsoft Support has confirmed that there is currently no supported native Power BI solution for dynamic SQL LIKE wildcard filtering at scale and recommended submitting this requirement through the Microsoft Fabric Ideas portal for product team evaluation.
Retain Matrix/Table Scroll Position When Returning from Drillthrough
Description: Currently, when users drill through from a Matrix or Table visual to a detailed page and then use the Back button to return, the report navigates back to the source page but resets the Matrix/Table to the top instead of preserving the user's previous position. This can be frustrating when working with large datasets, especially when the selected row is far down in a long Matrix or Table. Users must manually scroll and relocate the exact item they were analyzing before continuing their work. Suggested Enhancement: When returning from a Drillthrough page, Power BI should restore the original visual state, including: Scroll position within the Matrix or Table Expanded/collapsed hierarchy levels Selected row or record Visual focus and viewport location Benefits: Improved user experience and navigation Faster analysis of large reports Reduced need for repetitive scrolling and searching More intuitive drillthrough workflow, similar to modern web applications that preserve page state Example Scenario: A user scrolls to row 250 in a Matrix visual, drills through to view transaction details, and then clicks Back. Instead of returning to the top of the Matrix, the report should restore the view to row 250 with the same hierarchy expansion state, allowing the user to continue analysis seamlessly. Business Impact: This enhancement would significantly improve usability for enterprise reports containing thousands of rows and deeply nested hierarchies, where users frequently drill through multiple records during analysis.
Power BI Desktop on macOS
Description Many organizations are increasingly adopting macOS as a primary endpoint platform. However, Power BI Desktop remains available only for Windows, forcing macOS users to rely on virtual machines, remote desktops, Windows devices, or limited web-based alternatives. We would like Microsoft to provide a native version of Power BI Desktop for macOS, enabling Power BI developers and analysts to create, edit, and publish reports directly from their corporate Mac devices. Business Impact Large enterprises are deploying growing numbers of managed macOS devices. Data analysts, controllers, and business users working exclusively on macOS cannot use the full authoring capabilities of Power BI Desktop. Current workarounds (Windows VMs, Azure Virtual Desktop, remote Windows PCs) introduce additional licensing, infrastructure, support, and security complexity. Web authoring in Power BI Service and Microsoft Fabric is improving but does not yet provide full parity with Power BI Desktop. A native macOS application would improve user experience, reduce operational overhead, and strengthen Power BI adoption in organizations with mixed Windows/macOS environments. Thank you for considering this request!
Retain Matrix/Table Scroll Position When Returning from Drillthrough
Description: Currently, when users drill through from a Matrix or Table visual to a detailed page and then use the Back button to return, the report navigates back to the source page but resets the Matrix/Table to the top instead of preserving the user's previous position. This can be frustrating when working with large datasets, especially when the selected row is far down in a long Matrix or Table. Users must manually scroll and relocate the exact item they were analyzing before continuing their work. Suggested Enhancement: When returning from a Drillthrough page, Power BI should restore the original visual state, including: Scroll position within the Matrix or Table Expanded/collapsed hierarchy levels Selected row or record Visual focus and viewport location Benefits: Improved user experience and navigation Faster analysis of large reports Reduced need for repetitive scrolling and searching More intuitive drillthrough workflow, similar to modern web applications that preserve page state Example Scenario: A user scrolls to row 250 in a Matrix visual, drills through to view transaction details, and then clicks Back. Instead of returning to the top of the Matrix, the report should restore the view to row 250 with the same hierarchy expansion state, allowing the user to continue analysis seamlessly. Business Impact: This enhancement would significantly improve usability for enterprise reports containing thousands of rows and deeply nested hierarchies, where users frequently drill through multiple records during analysis.
Restore Shape Formatting Options in Button Slicer Visual
In the July 2025 Power BI update, the Shape formatting option was removed from the Button Slicer visual. This change has significantly impacted the ability to customize the appearance of slicers, especially for users who rely on rounded or pill-style buttons for consistent UX design. While layout and style settings (e.g., Card vs Table) remain, they do not offer the same level of visual control previously available through the Shape dropdown or border radius settings. Existing reports still retain their shaped buttons, which confirms that the underlying formatting logic is still supported — it's just no longer exposed in the UI. This change: Reduces visual flexibility for designers. Breaks consistency with existing reports. Removes a feature that was widely used and appreciated. Request: Please consider restoring the Shape formatting option or providing an alternative method (e.g., via theme JSON or advanced formatting) to control button shape directly. This is a small but important feature for maintaining visual polish and user experience in dashboards. Thank you for your continued improvements to Power BI — this feedback comes from a place of appreciation and a desire to keep the platform as flexible and powerful as possible.Power BI UX Suggestion: Preserve Selection When Switching Between Report and Model Views
When developing a Power BI report, if I select a visual in Report View and then switch to Model View, the selected table/column context is lost and everything becomes unselected. This can be inconvenient for developers, especially when troubleshooting or working with complex data models. 💡 Suggestion: It would be very useful if Power BI could preserve the selected visual, table, or column context when switching between Report View and Model View. I believe this small UX improvement could make the development experience much smoother and more efficient. Microsoft/Fabric team — please consider this enhancement for future updates. Please vote if you like the idea.Power BI UX Suggestion: Preserve Selection When Switching Between Report and Model Views
When developing a Power BI report, if I select a visual in Report View and then switch to Model View, the selected table/column context is lost and everything becomes unselected. This can be inconvenient for developers, especially when troubleshooting or working with complex data models. 💡 Suggestion: It would be very useful if Power BI could preserve the selected visual, table, or column context when switching between Report View and Model View. I believe this small UX improvement could make the development experience much smoother and more efficient. Microsoft/Fabric team — please consider this enhancement for future updates. Please vote if you like the idea.
Default Scrollable Time-Series Charts to Most Recent Data
Currently, Power BI time-series charts always open scrolled to the earliest (leftmost) date by default, which is inconvenient for reports where users are interested in the most recent (rightmost) date. A setting such as "Default view to latest data" would improve usability and align with how most users consume trend data. Please add an option for time-series charts to: Set the default scroll position (earliest date or most recent date). Remember the last scroll position when navigating between report pages. This feature would significantly improve usability for time-series charts.
