At least as an option, allow fields to be ordered the same as the source query rather than alphabetical. This way they can be put in a logical and consistent order. Obviously, a workaround is to prefix each column name with a number but this is clunky, unattractive and a pain if the columns change often.
78 Comments
- ChristianDiscer
Advocate I
The task pane displays database fields in alphabetical order. Please allow the field list to be displayed in original, or database defined order. - pbiideas1New MemberFound a related idea: "Display field names in database, not alpha, order"
- aleksandarkostaNew Membercan you order variables in fields section as imported from Excel
- steve_gorhamNew MemberCurrently if you set the "Default Field Set" field order in an SSAS Tabular model, it is not utilized by Power BI in the Fields pane. It still only sorts alphabetically.
- fbcideas_migusrNew MemberWhen looking at the tables in the Relationships window - and to make new relationships - it would really help to show the fields in alphabetical order. It feels like I'm always going on a scavenger hunt when I'm trying to find a field because I have to scroll thru the entire list looking for it. This can be challenging and time consuming, especially with large tables. Thanks!
- vincentvanasperNew MemberWould really like this to be supported.
- jonathan_marti6New MemberGreat Idea, and possibly to group fields together as well?
- martint1New MemberSSAS Tabular has a "Table Detail Position" described as "...field ordering that define the default field set when visualizing this table in certain client tools". Surprisingly, Power BI is not such a "client tool". Frankly, quite odd, when you think of how closely related Power BI and SSAS tabular are underneath.
- martint1New MemberCross post https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/18355429-use-field-order-as-ordered-in-source-query
- mark-allen-perrNew MemberI agree that the 'default' order for "Fields" should be whatever it is in the source. There is a reason the source has the fields in a specific order, so changing it means the 'structure view' to the user has changed. Please keep the order the same by default, and then (maybe) allow changes to be modified to 'sorted A-Z', etc. Many thanks.
Recent ideas
Add Automated Pre-Upgrade Compatibility Assessment for Fabric Spark Runtimes
Microsoft Fabric should provide an automated compatibility assessment before a workspace, Environment, notebook, or Spark Job Definition is upgraded to a newer Fabric Runtime. Spark runtime upgra...mourakshit9 minutes agoNew MemberNew1View0likes0CommentsSupport Creator-Independent Managed Identity and Ownership Transfer for Fabric Operations Agents
Microsoft Fabric Operations Agents should support an enterprise identity and ownership model that is independent of the individual user who originally created the agent. Today, an Operations Agent r...mourakshit11 minutes agoNew MemberNew2Views0likes0CommentsAdd Centralized Health, Freshness Monitoring, and Alerts for OneLake Shortcuts
Microsoft Fabric should provide a centralized health-monitoring experience for OneLake Shortcuts across workspaces and data sources. As organizations adopt OneLake Shortcuts at enterprise scale, hun...mourakshit13 minutes agoNew MemberNew2Views0likes0CommentsAdd Schema Compatibility Policies and Breaking-Change Detection to Fabric Event Schema Registry
Fabric Event Schema Registry should support configurable schema compatibility policies so teams can safely evolve event contracts without breaking downstream Eventstreams, Eventhouse ingestion, appli...mourakshit16 minutes agoNew MemberNew2Views0likes0CommentsAdd Dry-Run Simulation and Historical Event Replay for Fabric Activator Rules
Fabric Activator should provide a dry-run simulation mode that allows developers to test rules against historical or sample event data without executing real downstream actions. Activator rules can ...mourakshit18 minutes agoNew MemberNew2Views0likes0Comments