Some users can't see values in a table, but every other visual and slicer on all other pages works

[MCMcMax]

Just got off a call with one my users where we had a very strange situation where she couldn't see any values in a table. The headings were all there and the slicers on the page too, plus everything else on every other page was working fine too. When I went in through my computer there were no issues.

We tried making sure every slicer on every page didn't have something selected to see if there was some link I wasn't aware of. I also downloaded from Power BI into desktop and re-published it, but it made no difference.

So basically, there's a table of data where a particular user can't see it, but others can.

Any ideas because I've got nothing left..;-)?

[MCMcMax]

Thanks again @otravers for your continued guidance on this. So I ended up duplicating the original page in desktop, deleting the original and then re-publishing. Just heard back from the user that it worked so all good here now 🙂

[otravers · Accepted solution]

You need to chase down where the "rogue filter" is coming from. I'd start by creating a new blank report page and copying/pasting the table in it to see if the problem persists. If that solves the issue, it means that you have a hidden visual somewhere in the initial report page. Use the Selection panel to find it from the View panel in Power BI Desktop.

[MCMcMax]

Hi @otravers - thank you, it looks like that is the case. There's a line of data that isn't there anymore that's filtering it. The next question is - how do you turn the rogue filter off - I've asked the user to try different things left clicking and right clicking, but we couldn't find a way to remove it...

[otravers]

Have you looked at the "Filters" icon in the corner of the visual to rule out beyond the shadow of a doubt that no filters, slicers, cross-filters, or drill-through filters are affecting the table? There are so many ways to filter visuals, including synchronization across report pages via bookmarks or hidden slicers, that I find I always use that feature whenever a user doesn't see the same results as the default published state.