Forum Discussion
Published Report Filters Differently than PBI Desktop
I logged in and checked my reports again and this is working correctly now on the services so something must have changed back. I just opened the same report that was incorrect before and it is correct now today.
I definitely hit the reset to default button, I kept that on there to highlight that I added a filter which is what caused the data to not match up; it's all correct before I add the filter.
I attempted to do a save as on the PBI report and upload a completely new report and it still had this issue. I even uploaded it from a different computer on an older version of PBI.
Each card visual is referencing multiple other measures I built (all just simple counts and sums)
Only after the last update in November is this not working anymore, I simply just went onto the services; without uploading a new version or anything; and it was showing incorrectly like this.
Hello RocketmanJP
I have tested the slicer on the service and it won't affect the result of the card. So the version issue you mentioned should not be.
What you said is a bit messy... So I want to ask
Did you add a filter in desktop or service?
The result doesn't match, so where(desktop or service) the data is correct?
If you update the desktop version but don't republish to the service, it won't affect the existing report in the service.
So what is the scene where the problem occurred, can you rephrase it?
Best Regards,
Community Support Team _ JaneyI will try to rephrase it;
Since the November 2021 update I am running into a bug where if you try to add any filter to a report that is published to the service it calculates everything incorrectly. Even if I upload the report with a filter already checked, it will come up showing incorrectly. On the same report in Desktop everything works correctly.
If you look back to my past posts you can see the screenshots I posted that show how the data looks different from PBI desktop vs PBI service (I did a save as, published the report to the service, and took the screenshots side by side to illustrate the bug).
Service: Desktop (correct) :
As you can see, same opp ID's being referenced, same filter. Only difference is that Service is calculating contexting incorrect since the update.
Simple test can't find the problem like yours:
What is the data source of the report that has the problem? Are you connected to the gateway in the service, can it be refreshed normally?
Do you mean that any newly created report will have this problem?
If yes, Can you provide your current desktop version and service version?
If possible, please provide a sample file with the problem (without privacy).
Best Regards,
Community Support Team _ Janey
