Feature Request: Better Export Experience for Live Connection Reports in Power BI
We would like to request enhancements to the export functionality in Power BI, specifically when using a Live Connection.
Currently, when users export visuals with the "Summarized data" option in Live Connection mode, the exported file includes column headers in the format TableName[ColumnName]. We understand that this is an expected behavior. This format is not user-friendly and makes it difficult for end users to interpret the data effectively. We kindly request the ability to export data using friendly column names as defined in the report visuals, even when using a Live Connection.
If implementing friendly names is not feasible at this time, we would like to propose an increase in the row export limit. The current limit of 150,000 rows without a Live Connection is restrictive for our reporting needs. We suggest increasing this limit to at least 500,000 rows, which would significantly improve the usability and value of exported data for our users.
Recent ideas
Improve Copy Job Validation Errors When Upsert Keys Are Missing
Improve Copy Job Validation Errors When Upsert Keys Are Missing Product: Microsoft Fabric Area: Data Factory – Copy Job Category: Error Handling / User Experience Problem When adding new tables ...jasonhorner2 hours agoRegular VisitorNew5Views0likes0Comments📉 How Would You Investigate a 20% Drop in Revenue?
A data analyst shouldn’t stop at identifying what happened. The real questions are: Where did the decline occur? → Why did it happen? → What caused it? → What should we do next? By analyzing regio...aliulmurtaza4 hours agoNew MemberNew5Views0likes0CommentsAdd “Don't show this again” option to Power Query Insert Step warning
When a transformation is performed while an earlier Applied Step is selected, Power Query displays the “Insert Step” warning every time. This is useful for new users, but becomes unnecessary for expe...bjs17467 hours agoNew MemberNew4Views0likes0Comments