Define default selection for a column in the model

[marco4]

Create a property that defines the default selection for a column in a table. It is very needed in Calculation Groups, but all the tables/columns of a model could benefit. If that column is not referenced in the report, it should be filtered by default. Ideally, the default is defined by a DAX expression, so that it could be adapted to the user connected to a data model dynamically. It is acceptable that there should be a single selection, it is not necessary to support multiple selections for this feature. If a slicer is applied to a report, it should provide the default selection, even though the user can make a different choice. This is the only change required to the report user interface layer of Power BI. This feature should be similar to the "default member" property in a multidimensional model.

[tiago_rente]

Another interesting scenario, would be to a add a default member for a perspective and also for a role.

[mark42]

Agreed. In particular needed for Time Intelligence.

[Luis_Quedas]

Agreed. Very useful...

[francesco1]

How to vote it? Cannot find a way F

[jani_zajc]

Agreed!

[John_Tunnicliff]

Well overdue in Tabular!

[ellen3]

This is a great idea -- and I applaud all the Power BI Product Team's efforts to make Power BI easier to use - they will pay off in market share and leadership in the analytics space. As more students look to corporations to gain new skills, many will gravitate to tools that are easier to learn. And small businesses need to take a very hard look at the TCO of Power BI - for us it meant coming "back to the garden" with an Azure / Windows VM, rolling out Power BI and then far more training than expected. The learning curve is unnecessarily steep and repetitive tasks such as Marco is pointing out should be high on the list for improving. Consider how many students are looking to corporations like Microsoft, Google, Amazon, Tableau for skills training - this is a huge opportunity for Power BI and it fits with Microsoft's ethos of empowering people.

[fbcideas_migusr]

This is very good for enforcing calculation groups to always step-in, giving my vote for this. But it also creates some questions for me. 1) Will this setting within the data model be imutable. Imutable in the way that it can be overwritten by filtering other values, but it can never be fully released. Or can it be released by adding a slicer with nothing selected (by unselecting the default selection). This is how I understod Marco. But will this also be true for the sidebar filters (visual level filters, page level filters, and report level filters)? 2) Does cross-filtering count as beeing filtered? I.E. if the column is cross-filtered, will the default filter be released or not 3) Another question is what behaivour we would like to have if we add another visual to the page with the column having a column with a model based pre-selected column as a category in this visual. Shall the default filter setting then be released or not.

[fbcideas_migusr]

Also... or am I steeling this tread... Applying this on calculation groups, we would like to secure that the users only selects one item. In the GUI you can configure most of the slizers as "Single select" or "Requires singels selections". Specifically for calculations groups you would like to enforce this from the model so that the GUI can pick this up and pre-configure the slizers. Is it needed to create a separate thread for this, or can it be handled within this case (if Marco agrees)

[christophe_pass]

This feature is so much needed. I miss this MD cube feature