Making it possible to use (reference) query objects in a data item, instead of only tables, makes it possible to create better, faster and reusable datasets.

Currently to be able to use Query objects as data items in reports that has to be done using AL coding, which is cumbersome and inefficient.

If a Query object would better support SQL joins, because there are issues in how it implements multiple-nested-joins, compared on how it works in a SQL statement, and if then a query could be used, out of the box without workarounds, as a datasource for reports (and maybe also pages and xmlports) that would make it possible to create reusable, and maybe extendable, datasets, or use them as a base for a 'dataset builder' framework.

I feel like it might be time to completely re-evaluate: Queries and Reports?

Maybe a Query is also not the best choice, maybe a completely new 'dataset' object might be interesting to consider? I'm just thinking out loud here.

On top of that, if dataflows would have a BC connector, the same queries (or api queries) can really become 'resuable' datasets and can also be managed (security, refreshing,...) outside of BC.

The tool to build the layouts could then be whatever you prefer: Word, Excel, Power BI Desktop, Power BI Paginated reports, and other real document reporting tools ;-)