Refresh in service fails after deleting a not used column from datamart

[LangGergely]

Hello, community,

I have a problem. I have a datamart, where a field has been deleted. My reports are dependent of this datamart. In the report the field is not used anywhere. In desktop the refresh is successful, however in the service the refresh fails. When I open the report in desktop, and I refresh the report, then I publish again to the service, it works.

Why is that? In this case I have to refresh all my reports in Desktop and publish it again, which is very time consumig. I have about 30 reports.

Is there a solution to fix this?

Thank you.

[rajendraongole1 · Accepted solution]

Hi @LangGergely - i guess,the underlying dataset in the Power BI Service may still be holding on to the deleted field. Even though the field isn’t used in the report itself, the dataset still expects it during the refresh process.

can you try to republish the dataset (by refreshing it in Power BI Desktop and uploading it to the service), the Power BI Service clears any metadata mismatch. A faster way to do this for multiple datasets would be to trigger a refresh for each dataset directly in Power BI Service. Again, this can be automated using PowerShell or the Power BI REST API.

or  you could script the publishing process using PowerShell or the Power BI REST API to reduce manual effort, especially if you have a large number of reports (around 30, as mentioned).

[rajendraongole1 · Accepted solution]

Hi @LangGergely - i guess,the underlying dataset in the Power BI Service may still be holding on to the deleted field. Even though the field isn’t used in the report itself, the dataset still expects it during the refresh process.

can you try to republish the dataset (by refreshing it in Power BI Desktop and uploading it to the service), the Power BI Service clears any metadata mismatch. A faster way to do this for multiple datasets would be to trigger a refresh for each dataset directly in Power BI Service. Again, this can be automated using PowerShell or the Power BI REST API.

or  you could script the publishing process using PowerShell or the Power BI REST API to reduce manual effort, especially if you have a large number of reports (around 30, as mentioned).

[LangGergely · Accepted solution]

Hello, rajendraongole1

That's a good idea, to only republish the report, without refreshing it in the desktop version it saves the 90 % or more of the time. Then I don't have to wait for the refresh in the desktop version, It's a so simple solution. I don't know why I didn't try this. I tried and it works.

Thank you for the (obvious) solution.