Add export data functionality in "Explore this data" environment.
"Explore this data" is a really great feature for ad hoc analysis, but my organization's end users have no interest because it has no export data capability. For my organization (and many others I suspect) ad hoc work ultimately happens in Excel and that will continue for the foreseeable future. Why can we not have the ability to export to CSV as we do in the reports we publish?
3 Comments
- andy_claphamNew Member
Yep - that would make explore data so useful, rather than having to save to a report each time.
Also would help to not limit export to 150K rows (or 30K for csv).
- fbcideas_migusrNew MemberStatus added:New
- dan7Advocate I
Gotta find a way to bump this idea up.
I think there is a very valuable place for this "Explore" item in the world of self-service that would complement dynamic power BI reports and Paginated reports. Especially with the addition of "Visual Calculations" this past July.
As the data culture matures in an organization, ad-hoc self-service table and visual building with the ability for them to export the results to excel or csv may help new user confidence in migration to the broader Power BI and Fabric toolset.
Recent ideas
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 may be bound to a separate Fabric data connect...frithjof_v1 minute agoCommunity ChampionNew0Views0likes0CommentsBulk 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 ...vishal1401973 hours agoFrequent VisitorNew3Views0likes0CommentsAbout "Download SQL database project" and fix the downloaded project
1. The sqlproj must be fixed, it is downloaded without the xml markup line <?xml version="1.0" encoding="utf-8"> 2. The sdk must be updated: Actual: <Sdk Name="Microsoft.Build.Sql" Version="0.1...Jarrinf13 hours agoFrequent VisitorNew48Views3likes2Comments