Microsoft Idea

on 18 Oct 2024 21:47:28

RE:

Headers should be removable in table.

on 18 Oct 2024 21:33:50

RE:

In a multi rows card allow for the following
1. Increase no of Columns
2. Change orientation (Vertical / Horizontal)
3. Label (instead of only the measure name)
4. Format numbers individually

on 18 Oct 2024 21:29:45

RE:

Now we start and end point in the axis, It would be great if we have Interval between the start and End value
For eg: 0 is my start and 100 is my End means , I explicitly what the interval is 9, so that I can see my axis drawn like 0,9,18,27...99.

on 18 Oct 2024 21:25:37

RE:

We often have columns or measures that we want to be formatted the same in EVERY report tab in EVERY visual the same way. There is no universal method to format a measure in every visual in a report. We have to go into each visual on each report tab and do the exact same field formatting (colors, etc.) in each visual. We would like there to be a Universal option.

And, you know what will come next? :-) No doubt, somebody will want the formatting to be report wide EXCEPT for one single visual somewhere. Is that possible too?

on 18 Oct 2024 21:19:08

RE:

The recent addition of conditional formatting for values is wonderful. However, it would be great to have the ability format subtotals and totals, as the variation on those fields are often even more important to draw attention to.

on 18 Oct 2024 21:19:08

RE:

The ability of conditional formatting in matrices for values is wonderful. However, it would be great to have the ability to format subtotals and totals also, as the variation on those fields are often even more important to draw attention to.

on 18 Oct 2024 21:14:08

RE:

Allow a user to set the default value for a slicer or tile-by value on a page/dashboard, so that when the Power View page is opened for the first time, the default value is selected.
eg. If the page has a slicer for Year or Month, allow the user to configure the most recent Year or Month to be selected by default.

on 18 Oct 2024 17:03:43

RE:

Vote on this idea if you want expand/collapse on column headers in the matrix similar to what was shipped for row headers in November (https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-november-2018-feature-summary/#expandCollapse).

Ikshwak Reddy Kuchikulla on 18 Oct 2024 14:47:45

RE:

This functionality is crucial as it allows for the ownership of a created lakehouse to be changed through a UI/REST API. Our organization has a strict policy that production objects should not be owned by individual user accounts. Please kindly provide a timeline on when this would be available.

Kieran Leigh on 18 Oct 2024 14:27:55

RE:

This seems to be the default behaviour in Power BI. Even where rows differ, if you only add columns where they are the same, you get just the unique rows. The way round this is to add some kind of key column, which forces all rows to be displayed. The simplest way to do this is add an index column in Power Query. This is of course not ideal, using canvas space to show an unneeded field just to force a behaviour. I mentioned this in the Visual Calcs feedback thread. That update introduces the concept of hidden columns. Unfortunately, it did not allow it for all scenarios, though it would be useful in cases outside the scope of visual calcs. I can't say that development is planned, but do know this scenario has at least been seen by a product manager.We have a similar case - for audit, rows must always be displayed separately. Currently, a compound key is displayed in the column to ensure this is the case. This is also needed to provide the hook for drill-through pages. This would in our case be fixed by allowing columns to be hidden without alteration of the underlying table. Other people may find they do not have a key field and would like an option to force rows to never combine.