Data Not Displaying When Selected

Hello,
I'm not completely sure of the exact cause, but this usually points to a data issue rather than a slicer bug.

The most likely culprit is a mismatch in the London value. Even if it looks identical, there could be a hidden difference like a trailing space, a case difference, or an extra character that Power BI treats as separate . Since the query editor filter works, the data is definitely there, but the slicer might be pointing to a different London entry.

What I'd try: in Power Query, clean the area column by trimming and removing extra spaces. Also check if there's a second London value hiding in the slicer, maybe under a blank or different formatting.

Another possibility is a relationship issue. If the relationship between the area dimension and the fact table is broken for that one value, the slicer would still show London but return nothing . Check the relationship settings and make sure it's active and the cross-filter direction is correct.

As a quick diagnostic, create a simple table visual showing the area name and a count of fact rows, then filter to London. If the count is zero, you've confirmed it's a matching problem.

Best regards,

Daniele

Hi Lucy01​,

this points to a text mismatch between the slicer value and the data model, not a relationships issue, since it only breaks for London specifically and filtering in Query Editor to "London" still works.

Most likely cause: there's a hidden character, trailing/leading space, or inconsistent casing in the "London" value coming from a different source than you think (e.g., your slicer field is pulling from a dimension/lookup table, while sales data has "London " or "london" with different formatting). The query editor filter works because it's filtering the raw column directly, but the slicer relies on the relationship between two tables matching exactly.

To fix:

1. Check if your slicer field comes from a separate dimension table rather than the fact table itself, if so, compare the exact text value for London in both tables.
2. Use TRIM() and CLEAN() in Power Query on both the slicer source column and the fact table's area column, then reload.
3. If it's a direct text match issue, try LOWER() on both sides in Power Query to rule out casing differences.

This almost always comes down to the slicer's source values no longer exactly matching the fact table after a recent data refresh, even though both "look" like London to the eye.

Hi Lucy01​ ,
This is more like the value mismatch in fact and dimension table, there is set by step guideline to confirm this micmatch.

First create one temporary measure

London Sales = CALCULATE( [Total Sales], 'Area'[Area] = "London" )

Then create another measure 

Selected Area Sales = [Total Sales]

Place both measures in the table.


if london sales return values but Selected Area Sales returns 0 when london is selected in the slicer, the problem most likely is the filter propogation/relationship, not the data itself.

Further if above test does not conclude anything then check spaces in the area column , like if you have space the you need to clean those columns by adding text.trim(area) in Power Qurey.

If this helps, ✓ Mark as Kudos | Help Other

I've since found that this happens with another Area as well (Glasgow) so as a test I removed all data from my spreadsheet besides London & Glasgow. The London data displayed in the month over month chart, but Glasgow returned no values.

I've trimmed & cleaned the text and made sure the casing matches. I can't find any discrepancies in the data, but I'm not sure why it isn't displaying accurately

Suggestions welcome, thank you

Hi,

Please share some data to work with and show the problem there clearly.