HELP ! Table does not refresh on Services but does on Desktop

[Saraneh]

Hello everyone, 

I have a weird issue where a table in my report doesn't refresh in PBI Services. It does refresh on desktop, the source parameter in power query "UseStorageApi" is set to false.

There are other tables in the report, all the tables have the same source, same parameters. They are all up to date GCP tables.

I publish the report from desktop to a workspace dev online, then I deploy from dev to UAT and Prod with a PBI pipeline. 

I scheduled a refresh everyday, it ends succesfully but all of the tables refresh except the one ! 

I tried changing some column names in the table to force a new deploy in the pipeline, changed the report name... nothing works. The table is up to date the day I deploy it on Prod and the next day it's not anymore. It doesn't refresh even with a manual refresh. It's driving me crazy !

Do you have any clue what the problem is ? 

[Saraneh · Accepted solution]

Hello everyone, 

Turns out my issue was simpler than expected, the 'Include in report refresh' option was unchecked on that table.
We had just switched the dashboard to PBIP and published it for the first time in that format, which misled me into thinking it was a bug related to the file format or the deployment pipelines.
Lesson learned: Always double-check the basics before jumping to complex explanations.
Thank you all for the help !

[v-echaithra]

Hi @Saraneh ,

Try rebuilding the query from scratch as part of the debugging process, and let me know how it behaves afterward,

Do NOT duplicate the existing query, that may retain internal IDs or stale metadata. Instead, create a brand new blank query (Home > New Source > Blank Query).
Manually write or reconstruct the M code type it out or paste in parts, testing as you go.
Load it with a new table name. Then load to the model > publish > test refresh.

This can solve cases where the query is invisibly corrupted at metadata.

[v-echaithra]

Hi @Saraneh ,

Sometimes residual metadata or broken lineage tags in the Service-side dataset block correct table updates, and only a full reset clears it.

Export your current PBIX

Delete the dataset in Prod manually once

Re-publish through the deployment pipeline (Dev > UAT > Prod)

Best Regards,
Chaithra E.

[Saraneh]

Hi @v-echaithra ,

Thank you for the help, I tried your solution in many ways 🙂 :

- deleted the dataset and report manually in Prod and UAT and redeployed --> didn't work, tables not refreshed manually or automatically 

- deleted the dataset and report manually in Prod and published directly in Prod to work around the pipelines--> didn't work either

- published the dataset and report with a new name and in pbix format. Then deployed with the pbi pipelines --> didn't work either.

I'm out of ideas and don't know how to move forward.

[Akash_Varuna]

Hi @Saraneh It might be due to inconsistent refresh mechanisms in Power BI Service. Ensure the table query doesn’t reference multiple sources without combining steps properly. Try setting UseStorageApi to true, as its default behavior supports most storage scenarios unless you're using the REST API explicitly. Confirm consistent credentials and permissions for the affected table in all environments.

[Saraneh]

Hi @Akash_Varuna , thank you for your reply. 
I confirm that there's only 1 source, and cosistent credentials and permissions for that table. 
I tried to turn UseStorageApi to True, it didn't work either. 

I'm open to further ideas!