Power BI Dataset Refresh Succeeds but Specific Timestamp Rows Missing After Refresh

[KanchanGiri_121]

Hi,

I’m facing a strange issue with a Power BI dataset refresh and wanted to check if anyone has seen something similar.

The dataset is set up with scheduled refresh in Power BI Service, and the refresh completes successfully no errors at all. However, after the refresh, I can see that some rows tied to a particular timestamp are missing from the report.

I’ve already validated the source system, and those records are definitely still present there. So the data exists in the source, but somehow doesn’t make it into the dataset after refresh.

A few more details:

• Incremental refresh is not enabled

• No refresh failures or warnings

• The missing rows are always linked to the same timestamp

This is impacting the accuracy of the dashboard, so I’m trying to understand what could cause this kind of behavior.

Has anyone experienced something similar where specific rows disappear even though the refresh shows as successful? What areas should I investigate?

Any guidance would be really helpful.

[v-hjannapu]

Hi @KanchanGiri_121,

I would also take a moment to thank @GeraldGEmerick , @Natarajan_M for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Regards,
Community Support Team.

[v-hjannapu]

Hi @KanchanGiri_121,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.


Regards,
Community Support Team.

[KanchanGiri_121]

Hi @v-hjannapu,

Thank you for checking in and for all the support so far. I truly appreciate the help from you and the community.

I’ve gone through all the suggestions that were shared and double-checked everything on my end. Unfortunately, the same timestamp-specific rows are still missing after the refresh in the Service, even though the refresh completes successfully.

At this point, I’m not sure what else could be causing it. If there’s anything additional you’d recommend looking into, I’d really appreciate your guidance.

Thanks again for your help.

[v-hjannapu]

Hi @KanchanGiri_121 ,
Since the refresh is successful and you have already checked everything from your side, this may need deeper investigation from the backend. I would suggest raising a support ticket with Microsoft Support so they can review the detailed refresh logs in the Service.

Please refer below link on how to raise a contact support or support ticket. 
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn 

Regards,
Community Support Team.

[KanchanGiri_121]

Hi @v-hjannapu @

Thank you for your guidance and support on this.

I appreciate your suggestion — I will go ahead and raise a support ticket with Microsoft Support for further backend investigation.

Thanks again for your help!

[Natarajan_M]

Hi @KanchanGiri_121 ,

it seems that some records might have been filtered out.
1) Copy the query for that table and create a new blank query in the desktop file. Select the desired timeframe and check each step to identify where the filtering is occurring.
2) Before performing the first step, verify in the report you are validating whether there are any pre-selected filters that could be blocking the records from being displayed.
3) In Service, the date and time are provided in UTC by default. If you use a function like now(), it will also return time in UTC. If your data is in a different time zone and you are filtering the data based on date time , this could also cause discrepancy 

Thanks

[KanchanGiri_121]

Hi @Natarajan_M,

Thank you for your suggestion and for taking the time to help.

I’ve reviewed the report thoroughly and don’t see any report-level, page-level, or visual-level filters that would be excluding records. I also checked the query steps in Power Query, and there doesn’t appear to be any explicit filtering removing those rows.

At this point, I’m not able to identify where the discrepancy is occurring. Please let me know if there’s anything specific you’d recommend checking further.

[GilbertQ]

Hi @KanchanGiri_121 

Can you please confirm that when looking at the report in the Power BI service that you have clicked on the reset to default option as sometimes in the past there are filters that are being applied which are not easily visible which is causing it to appear like the data is incorrect?

The reset to default button looks like the following below:

[KanchanGiri_121]

Hi @GilbertQ,

Thank you for your suggestion and for taking the time to help.

I’ve checked the report in Power BI Service and used the Reset to default option. The issue still persists, so it doesn’t appear to be related to any applied filters.

I’d welcome any further suggestions on what I could validate next.

[GeraldGEmerick]

@KanchanGiri_121 If you download the report and manually refresh, do you get any refresh errors? Sometimes the refresh can succeed but certain individual rows fail to load but that does not fail the entire refresh. Are you doing any error handling as part of your query, such as "Remove errors" for example or try blocks in your M code?

[KanchanGiri_121]

Hi @GeraldGEmerick,

Thanks so much for your suggestion and for taking the time to help.

I did try manually refreshing the report in Desktop and checked for any row-level errors. I also reviewed the queries to see if there were any “Remove Errors” steps or try/otherwise logic in the M code.

I even disconnected and reconnected the data sources to make sure it wasn’t a connection issue, but unfortunately the problem is still happening.

Please let me know if there’s anything else I can check. I really appreciate the help.