Forum Discussion
BigQuery data doesn't reflect in the report correctly
Hi Tani4ka
Since we have ruled out common causes such as credential re-authentication, dataset refresh behavior, and discrepancies between Power BI Desktop and Service, and the issue persists, it seems a deeper investigation into your specific environment and dataset configuration is necessary.I recommend raising a support ticket with Microsoft for a more detailed analysis. The support team can access backend logs and provide targeted assistance to resolve the issue.
You can submit a ticket through the Microsoft Power BI Support Portal:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you!
I'm afraid it is not the case. The latest date i see in the report is 4th April but in GBQ is 9th April. I do not rely on the CURRENT_DATE() . With desktop version i see the 9th stright away and when published as well. But in order to see the next day again (lets say the 10th tomorrow) i have to refresh tomorrow in the desktop and republish. Any other suggestions? Would be very gratfull. Thanks.
Hi Tani4ka
Despite the scheduled refresh running successfully, the underlying data is not updating in the Power BI Service.
If the dataset is in Import Mode, Power BI loads a snapshot of data at the time of refresh. If the service refresh is not actually fetching new data from BigQuery, stale data will persist.
When you refresh in Desktop and publish, the refreshed model is uploaded to the Service that’s why it shows the latest date. But the Service refresh isn't truly refreshing the model.Try re-authenticating the Google BigQuery connection, even if it appears valid. Then refresh it in service. Check whether it resolves the issue or not.
If this post helps, kindly mark it as Accepted Solution.
Thank You!
I'm fraid it did not resolve the problem for me
Hi Tani4ka
Since we have ruled out common causes such as credential re-authentication, dataset refresh behavior, and discrepancies between Power BI Desktop and Service, and the issue persists, it seems a deeper investigation into your specific environment and dataset configuration is necessary.I recommend raising a support ticket with Microsoft for a more detailed analysis. The support team can access backend logs and provide targeted assistance to resolve the issue.
You can submit a ticket through the Microsoft Power BI Support Portal:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you!
Hi Tani4ka
Could you please confirm if you have raised the support ticket and if the issue has been resolved after raising a support ticket? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you !