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 support for identity columns in Fabric warehouses.
Identity columns are a common method for generating surrogate keys in data warehousing scenarios implemented on SQL Server. By adding support for identity columns in Fabric, users could migrate the...dpurdy1 hour agoRegular VisitorCompleted4.4KViews131likes11CommentsFabric UX Idea: Clearly Identify the Source Workspace for Opened Fabric Artifacts
In many Fabric implementations, organizations have multiple projects and environments, for example: Sales Analytics – Development Sales Analytics – UAT Sales Analytics – Production Similarl...Murtaza_Ghafoor7 hours agoSuper UserNew5Views0likes0CommentsCopilot in Power BI should be canvas-aware and support screenshots / direct visual debugging.
Currently, Copilot in Power BI cannot: See the actual canvas / selected visual Accept screenshots or images to aid in troubleshooting Both of these make debugging visual-level issues painful and...dcohare7 hours agoHelper INew8Views1like0Comments