The Applied Steps pane on the right (in Power Query) auto generates step names using normal spaced words. This is great when reading the step names in this pane. There is, however, an unfortunate consequence of this naming style. The M Code is more difficult to read and write (although reading is the main issue I see).
Here is an image showing the difference in readability between the 2 approaches.
- cristian_angya24 years agoNew Member
Love the Idea Matt!
I'll do my best to spread the word and get more votes on it!
- fbcideas_migusr4 years agoNew Member
+1 vote
- excelworld4 years agoNew Member
Voted & Posted on my social media accounts
- kbarber13 years agoNew Member
I am the opposite. I use #"" for all variable names, even those that do not contain spaces or special characters. I find this to be easier than needing to remember the 2 possible syntaxes. Also, the #"" adds some visual bulk that makes the variable names stand out a bit better. Whenever I see #"", I know that I'm looking at the name of a query, variable, column, or field. Lastly, #"" lets me write the variable name however I want without restrictions like needing to not use spaces or special characters. You are no longer forced to write like a programmer. You can write largely like you normally would and your code will still be valid, and I think that this is great.
In the image that you shared, the camel-case step names in the pane are harder to read than the default names. The solution is not camel case. The solution is to have a way to get the effect of #"" while still being easy to type and easy to read. Maybe something like surrounding the variable name in single quotes is the solution (e.g. 'Variable Name').
- fbcideas_migusr1 year agoNew MemberStatus changed:NewtoNew
- miguel3 months agoCommunity AdminStatus changed:NewtoNew
Recent ideas
Support Git-Integrated Files in Fabric Workspaces
Overview Allow users to store and manage arbitrary files such as .md, .sql, .py, and .yml directly in a Fabric workspace, with built-in Git integration. Value This would keep documentation, SQL sc...ryomaru08252 hours agoAdvocate INew26Views4likes1CommentConsistent Locale Handling Across Power BI, Fabric, PowerPoint, and Subscriptions
Microsoft Fabric and Power BI should provide consistent locale handling across all user experiences. Today, locales such as German (Switzerland) are correctly respected in Power BI Desktop and the Po...Le_M4 hours agoRegular VisitorNew17Views1like0CommentsIn Data Pipelines, Schedules should not be part of the definition
The request is to ensure Schedules are not included in the definition of a Data Pipeline for purposes of Deployment Pipelines. Today, when we deploy content across environments, the item frequent...schneiw4 hours agoAdvocate IVUnder Review813Views25likes3CommentsPipeline activity Refresh SQL Endpoint (preview) does not accept dynamic content
I am testing out the new Pipeline activity for Refresh SQL Endpoint, currently in preview. Sure, I get it that this is in preview, but it should at least have basic minimum functionality. It do...ToddChitt5 hours agoSuper UserNew589Views8likes6CommentsPower BI Admin & Governance Center – Centralized Activity and Usage Analytics
Subject: Feature Proposal: Advanced Power BI Admin & Governance Center – Centralized Activity, Access, Sharing, Licensing and Usage Analytics Dear Microsoft Power BI Team, I would like to propose a...Dr7awb9 hours agoNew MemberNew6Views0likes0Comments