Forum Discussion
Strange filtering issue once published
I am bumping up against something weird I am hoping someone has seen before.
The two pictures below are from the exact same file and dataset. One (the top one) is shown in Desktop, the other published an viewed in Service (a browser).
The published one (on the bottom) is successfully refreshing. No errors. FIlters are exactly the same (date range set via New Filter Experience). Zero files changes between the two, but as you can see the published one cuts off the last two months. Again, there are NO errors, it just behaves like the dataset has nothing after OCtober 31st, which is not the case because the Desktop is pulling from the exaxt same remote source. Not a copy of it, but the same actual source.
This is happening across this entire report, so it's like there's a higher-level filter (just on this report) that I cannot find. Have you ever seen a report act like it’s filtered differently or missing data once it’s published (but works OK in Desktop)?
- Hi Anonymous ,I have tested with my file but not reproduce the issue.You can try the following steps:1. Check the version of power Bi desktop and republish the report2. If the problem persists,please click on this button3. You can also bookmark this visual on desktop:Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
- V-lianl-msftCommunity SupportHi Anonymous ,I have tested with my file but not reproduce the issue.You can try the following steps:1. Check the version of power Bi desktop and republish the report2. If the problem persists,please click on this button3. You can also bookmark this visual on desktop:Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.- AnonymousNot applicable
Amazingly, simply clicking the "Reset to default" appears to have fixed it.
Since I have no filters that limited the dataset to that timeframe I have to assume it was somehow corrupted. (?)
At any rate, I'll monitor and post again if it comes back
Thanks!