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
- ChristianDiscerAdvocate IThe 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
Allow External OneLake Data Shares to Be Accepted into Multiple Fabric Item Types
Fabric External Data Sharing provides an excellent zero-copy mechanism for sharing OneLake data across tenants. However, the receiving tenant currently has to accept the share into a Lakehouse. I w...Mourak10 hours agoNew MemberNew5Views0likes0CommentsAllow OneLake Shortcut Authentication Mode to Be Changed In Place
OneLake shortcuts support passthrough and delegated authentication, but changing the authentication model currently requires deleting and recreating the shortcut. I would like shortcut authenticatio...Mourak10 hours agoNew MemberNew7Views0likes0CommentsTenant-Wide OneLake Shortcut Lineage and Impact Analysis
This is grounded in a documented limitation: shortcut lineage is currently workspace-scoped, and Microsoft specifically says lineage for shortcuts to warehouses and semantic models isn't currently av...Mourak10 hours agoNew MemberNew12Views0likes1CommentAdd an End-to-End Production Reference Architecture for Microsoft Fabric Real-Time Intelligence
I would like to see a complete end-to-end Microsoft Fabric Real-Time Intelligence reference architecture that demonstrates how the individual RTI capabilities work together in a production-oriented s...Mourak10 hours agoNew MemberNew5Views0likes0CommentsImprove CI/CD consistency for Microsoft Fabric Real-Time Intelligence Eventstreams
Microsoft Fabric Real-Time Intelligence has made strong progress with Git integration and deployment pipelines, but lifecycle management can still be inconsistent across Eventstream sources, destinat...Mourak10 hours agoNew MemberNew3Views0likes0Comments