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...
LissHay
5 years agoNew Member
Database fields in a table are always created in a specific order. When working with the tables in BI it creates an unnecessary unfamiliarity when working with the tables, especially when you are used to working with them in their designed order. I agree with an earlier comment, the original order should be the default, and alphabetical order an option. Especially when working with databases.
Recent ideas
Add "Collapse all / Expand all" to the Queries pane in Power Query Editor
Hi Fabric Community, I suggest adding a "..." menu beside Queries(n])with Collapse all and Expand all. Current state: With many queries, every group and Helper Queries folder is expanded. My 8...DataVitalizer1 day agoSuper UserNew13Views0likes0CommentsAdd 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...mourakshit1 day agoNew MemberNew6Views0likes0CommentsSupport 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...mourakshit1 day agoNew MemberNew11Views0likes0Comments