Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
I have a report that is a direct SQL connection. I have been using it for many months without problems. This is what the data looks like in the desktop app.
In the service the data for the 28th May is not there, but it is included in the total. I have republished from the desktop app to the service.
When I look at the App I have for this the data shows in the App. So it just missing from the Service.
I have republished from the desktop app to the service. and checked all the filters as they are the same.
Any suggestions?
Solved! Go to Solution.
I have resolved the issue. There were two slicers on the page, both independant, so I thought. One of the slicers was impacting on the other one unexpectadly. I recreated the report from scratch and it identified the slicer issue which I then isolated out. Thanks for those that helped.
I have resolved the issue. There were two slicers on the page, both independant, so I thought. One of the slicers was impacting on the other one unexpectadly. I recreated the report from scratch and it identified the slicer issue which I then isolated out. Thanks for those that helped.
Hi @AmandaHore,
I'm glad to hear that your issue was resolved. Please mark your reply as the solution so it can help other community members facing the same issue.
Thank you.
Great to hear this is resolved!
The SQL login is provided to us via a vendor and has full access to all data. Can you explain more about how the Power BI service using Azure AD identity? Or send me a link so I can read up on it.
When using Power BI service, you are logged in with your organizational/Azure AD account (e.g. yourname@yourorg.com). This login is different then the login you are using when you are on desktop. In Power BI desktop, since you are using the SQL login and a different set of credentials, that login might have full access.
However, once you are in service, your organizational account may have different data access. It is possible your IT department may have changed security around this recently. Is there any potential linkage to the rows you can and cannot see such as organizational heirarchy or department?
Additionally, here is some official Microsoft documentation around Power BI security and user authentication: https://learn.microsoft.com/en-us/power-bi/enterprise/service-admin-power-bi-security
If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.
Thanks,
Samson
We are a small company and I am the IT department 😁
I have system admin access using my organisation credentials inside the App so I should have no problems seeing this data. I can see if through the app front end all ok.
I will keep digging and see if there is something unique about that particular record.
Hi @AmandaHore,
Thank you @SamsonTruong, for your insights.
Thank you for reaching out to the Microsoft Fabric Forum Community.
Please check if there are any hidden filters at the visual level in the filter pane, as this filter can sometimes cause an issue.
Additionally, check the relationship between the tables in the data model, as this can also cause an issue.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
There is nothing in those items. I have noticed that the issue is for certain named individuals. It use to work in the report and now does not. I have logged a ticket with the vendor of the application this data comes from, and who provide the SQL logins to see if they can identify a potential change in their system that could be causing this.
The vendor that runs the SQL database have confirmed there is no row level security within the database.
I have just republished the report from Desktop to service, with no change.
I am struggling to understand why the data is different between the desktop versus the service
Hi @AmandaHore,
Power BI service saves the state of your filters from the last time you visited the report in service. Most likely, this may be caused by different filtering in service and in desktop.
I noticed you mentioned checking all filters and ensuring they are the same. By any chance, have you also checked the underlying filters such as visual filters and other filters that may occur in the filter pane.
I noticed that in your screenshot, the date ranges on the slicer differ between service and desktop.
If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.
Thanks,
Samson
yes I have checked all of those. The item appears to be included in service by looking at the totals, but just not in as an individual line.
Thank you for validating. My next guess would be there may be some level of row-level security on the data source end that could be masking certain rows once the data hits Power BI service. What authentication method are you using to establish the SQL direct query in Power BI desktop?
In Power BI Desktop, if you're connecting using your local Windows or SQL credentials, the source might be allowing you to see all rows. In Power BI Service, the connection is made on your behalf using your Azure AD identity. If the source SQL database has any user-based filtering or row-level logic, it may exclude certain rows based on how your identity is passed through when the report is run in the Service.
The App view may still show the row because it could be cached from an earlier publish before any security rules took effect, or your access permissions in the App differ slightly from the Service workspace view.
If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.
Thanks,
Samson
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!