The reason I suggested the signature as I did, in contrast to the suggestion by Kishor Mistry, is that the number of fields that should be sorted on is probably dynamic and set by some kind of data in the database and thus cannot be added as parameters to the same function call.
Looping the fields and calling RecRef.SetAscending() for each field would be more useful, IMO.
The reason I suggested the signature as I did, in contrast to the suggestion by Lourens Vlaanderen, is that the number of fields that should be auto calculated is probably dynamic and set by some kind of data in the database and thus cannot be added as parameters to the same function call.
Looping the fields and calling RecRef.SetAutoCalcField() for each field would be more useful, IMO.
Add a Table Action option for Incremental Load.
- Let the user identify the Primary Key column(s) from the source (or read meta data from source)
- Add some auditing columns (is current, is active, is deleted, load date, update date, current key)
- Add new rows, update existing rows, mark deleted rows.
Or is some of this plumbing already taken care of by the delta tables?
Not sure how anyone could even use the App without this technical ability.
Very important feature. Much needed.
I would say it has to support publish-to-web if Microsoft is sunsetting the old map visuals per this blog post: Power BI May 2023 Feature Summary | Microsoft Power BI Blog | Microsoft Power BI
How easy would this be for Microsoft to fix ?? Five years and we are all still complaining about the LONG date default formatting which I swear absolutely NOBODY PREFERS ! Microsoft, you're killin me!!
A must have - to improve user experience and reduce multiple tabs being opened. The PBI navigation panel is great, but having this same functionlity as standard within a button or Web URL link is going to be critical to roll out anything substantial, consisting of multiple dashboards to a large set of users.
Not sure why this feature was revoked in a prior version - this is a common feature in most of your competitors' products and really frustrating that we need workarounds in DAX to accomplish such a simple feature. Such breadth of workarounds could also skew the usage data when the prior histogram feature was released (i.e. many users didn't have time to upgrade their many work-around histograms to the new feature but still need a streamlined feature for new analytics applications).