Can this feature interest you ? Why supporting DAX against tabular models ? Why ETL on top of a cube supposed to already be ETLized ? Here are the reasons :
whatever you can design in your cubes, people will always have to transform the data. Today Power BI can do that by importing part of a cube, one dimension after the other, itβs not so convenient.
make easymorph the only tool for all data sources. One cube is a major data source that forces users to use other ETL compatible tools.
because itβs simple ! Itβs a quick win. I mean you are not forced to apply all query editor features. It would just be selecting fields and applying simple filters (without custom SQL for example).
because a cube is not only for analytics, itβs also a way to provide a data model, and to provide good performance depending on the join defined inside the cubes, even more if you handle data in memory. Itβs just a performant database to query ! When developpers provide a cube, they also hope it to be one unique data access point.
because DAX has become a worldwide language, and itβs not complex to manipulate for this use case.