Is there a way to rename the 'Blank' value in a slicer?

[Anonymous]

While I actually do need the "(Blank)" value in my slicer, I'd like to change its name to something like "Unknown" for my application. Does anyone have any ideas?

Much thanks, in advance.

-Jude C.

[BhaveshPatel]

Hi @Anonymous,

There are many ways you can use to change the blank values depending on where your source data is flowing from.

The handy way I use is to use the Replace Values in the Query Editor to change the name to Unknown instead of Blank Values.

Thanks,

Bhavesh

[Anonymous]

Just a quick qualification, all: I'm trying NOT to use the Query Editor for this purpose, because I'm looking for the remainder between columns of two very large tables, and the range of values within that remainder could vary widely. I just want to be able to rename the '(blank)' value on the front-end slicer to something a little more intuitive to the user.

Let me know. Hope you're having a great weekend.

-JC

[PaulDBrown]

@Anonymous

Probably not ideal, but how about duplicating the column in query editor (or as a calculated column), replacing the blank values with some other useful text, and use this column in the slicer, and the original column for calculations?

Clumsy, I know, but...

[freder1ck]

When trying to avoid increasing query load time, this is the solution. In the transaction table, you can do a calculated column with LOOKUPVALUE() to the dimension and if ISBLANK() then, add "XXX" or -1, else use the returned value. On the dimension side, you will want to append a row in Power Query (not expensive for performance) with "XXX" or -1 as the key and "Unknown" as the displayed value. 

[MattAllington]

Hi @Anonymous et al.  Sorry I didn't get back to this post.  I see a lot of different ideas about how to fix this.  I want to put forward my view for your consideration.  I have created a blog article and video showing how I recommend you fix this.  You can see it here => Remove Blanks in Slicers in Power BI

[elietech]

This method is exactly what I needed.  Works great! Thanks!

[v-xjiin-msft · Accepted solution]

Hi @Anonymous,

I'm afraid that there's no way to rename the '(blank)' value on the front-end slicer side. All you can do is to replace the blank value at source data side.

Thanks,
Xi Jin.

[Anonymous]

I'm accepting this as the solution, since it's conclusive about what's actually possible. Thanks. -Jude C.

[Anonymous]

I used something like this in Modelling...

CompanyTypeLabel = IF(ISBLANK(LOOKUPVALUE(gap_type[gap_label],gap_type[gap_value],new_accountset[CompanyTypeValue])),"Business",LOOKUPVALUE(gap_type[gap_label],gap_type[gap_value],new_accountset[CompanyTypeValue]))

I've changed some of the field names involved, but it should be obvious what I've done.

[MattAllington]

The reason you have a blank is there is Data in the table on the many side of the relationship that has no matching record in the table in the one side of he relationship. To solve this, add the missing records to the one side table and give them any name you like. 

[vhatp]

May I ask (a few years after), how exactly would You achieve this? I've tried all of the following, to no avail.
Let's say, there are two categories of concern: A and B. There are also records that belong to none of them, they are listed as '(blank)' in PowerQuery (not 'null') and '(Blank)' in PBI.

I've set up a dimension table like this

data_value	cat_name
A	Letter_A
B	Letter_B
''	quotes
""	double_quotes
null	a_null
	empty_string

My problem is, the blank data would never get assiciated with any of the categories and the '(Blank)' group will still remain (if I chose to display items with no data).

How should I address the empty values?
Thanks in advance!

P.S. I know it would be wise to head back to PQ and replace the missing values with somenting more meaningful, perhaps even 'null', but the problem is, It would take several hours to refresh, which I am trying to avoid right now.

[Anonymous]

Thanks, Matt. Is there any way to do this purely on the front-end? The thing is I essentially want this to be a catch-all for all of those records whose column X doesn't match another table's records for column X, and I'd like to do this at scale.

LMK. I think the user group would be comfortable with simply using '(Blank)'. I'm just trying to make it all more intuitive.

Hope you're having a nice night/morning(?).

-Jude C.