I’d like to share my perspective as a user who’s proficient in SQL and other BI tools. While DAX is undoubtedly powerful in handling complex, context-aware calculations, it imposes a steep learning curve and obscures basic analytical logic. Tasks that should be straightforward — such as calculating Top N per category — require excessive workaround logic in DAX due to its rigid dependency on filter and row context. This breaks from common, transparent approaches used in SQL (e.g., using RANK() over partitions). My main concerns: The context-driven model makes even basic queries unintuitive. DAX requires more effort for simple outputs than equivalent operations in SQL, Excel, or Tableau. Visuals like Matrix don’t provide native support for “Top N per group,” forcing users to misuse DAX constructs. Request: Please consider adding clearer, user-controlled query constructs, or simplifying the interface for basic analytical patterns like Top N, rankings, and grouped aggregations — without requiring deep DAX expertise. DAX’s abstraction of “context” is clever, but in many scenarios it becomes an obstacle. A balance between power and usability would make Power BI more accessible and effective for all users — not just those who master DAX internals. Dear DAX developers, You’ve created a language so focused on internal “context” that you’ve lost sight of external usability. When experienced users — especially those fluent in SQL — can’t do basic Top N breakdowns without struggling against hidden logic, you’ve failed at interface design. Context shouldn’t override clarity. If your tool is powerful but not approachable, it’s not powerful — it’s exclusive.
... View more