RE:
this is such a useful feature, should have been included years back - causes a lot of problem when trying to scale dataflows with different access permissions.
RE:
Any updates on this? I have seen this as preview feature from version 41 onwards, but I cannot find it anymore, neither in the release notes nor in the feature list in the system.
RE:
Hi Andrei. It is not available.Please, do it asap.Thank you.
RE:
Basically, either include UpdateDatasources API Call also for Data lake or some other approach to change data lake URL and Credentials more easily to account for various environments with the same report model.
RE:
The sorting feature I asked for in the above suggestions is sorting subcategories based on the sales within each category.
RE:
See screenshots here: https://imgur.com/a/FKZHuD2
RE:
December 2024, still waiting on this. Getting ridiculous
RE:
RE:
I just want to add, since this idea is under review, that I hope Microsoft doesn't break the current implementation of how data is aggregated in Matrices. In fact, I am not even sure what everyone is complaining about. If you set up your parent-child hierarchies properly, then from my experience, Power BI does all the heavy lifting for you. And believe me, my matrices are incredibly complex from simple sums, counts, and averages to complex weighted averages and more and all in the same matrix. It is quite a marvel to see Grand Total metrics that are not only correct but never seen by anybody before. If the user can't understand why the Grand Total is not a sum of the rows, that's on them. If I had to write separate DAX measures to do all that math at the Grand Total level, I would go crazy. And if a user wants to reproduce that aggregating math in Excel, good luck, and this is from someone with over two decades of Excel engineering expertise including VBA. In my experience, this is where PowerBI really shines: its ability to aggregate which is really unparalleled, but you have to know what you're doing.
RE:
Our customers are waiting for this feature and must now choose extentions or customizations. We also need a sending profile per usage (e.g. invoice = mail and Sales Shipment = print and mail)