Forum Discussion
help in refresh in Power BI service
Hi Anonymous ,
Thanks for the update. The issue might be due to the old partitions that weren’t fully cleared before the refresh. When you disable incremental refresh and republish, the Service still retains historical partitions unless you explicitly delete them. Try these below steps by using some sample data.
Disable incremental refresh in Desktop and refresh locally.
Publish to Service, overwrite dataset.
In Power BI Service > Dataset Settings > Incremental refresh history,
Delete all partitions (this step is critical).
Trigger a full refresh in Service, this rebuilds schema without incremental logic.
Re-enable incremental refresh in Desktop, set RangeStart/RangeEnd, and publish again.
Run the refresh again in Service.
Hope this helps.
Thank you.
Hello v-echaithra , no unfortunately I did all the steps and it is not working however I changed the warehouse to PROD and it works. Error only when I am connected to UAT database it returns error in the mentioned column while this column is in removed step in power query.
Community SupportHi Anonymous ,
Thanks for the additional details, It's good to know that the issue only occurs with the UAT database, which helps narrow things down.
Since the error doesn't occur with the PROD environment, this seems to suggest that there might be something specific to the UAT schema or the data model in Power BI related to caching or metadata.
Try to clear the schema cache in Power BI Service for UAT. Double check the UAT schema in the source database to ensure that there are no lingering references to the UPD_DATE column, particularly in views or stored procedures that Power BI might be querying. You may run a query directly against the UAT database to confirm that the UPD_DATE column has indeed been removed from the source. Ensure that there isn’t any server-side caching or schema caching within the UAT database itself that might be causing Power BI to still expect the UPD_DATE column.
Since the issue is isolated to the UAT environment, consider any differences in the UAT database configuration or data source settings. Could there be some discrepancy in how the UAT and PROD environments are set up?
If the issue persists, consider publishing a fresh version of the dataset from Power BI Desktop to the UAT workspace, ensuring that all references to the removed column are cleared.
Ensure that incremental refresh is disabled before publishing, refresh once, then re-enable it and publish again.
Thank you.
Thank you v-echaithra , unless i miss something in my action: I disabled incremental refresh, published the dashboard then go to settings , parameters and put the rangestart from the 1st available date and then run the refresh ( run refresh of the complete dataset)
- v-echaithra
Hi Anonymous ,
Thanks for the update. The issue might be due to the old partitions that weren’t fully cleared before the refresh. When you disable incremental refresh and republish, the Service still retains historical partitions unless you explicitly delete them. Try these below steps by using some sample data.
Disable incremental refresh in Desktop and refresh locally.
Publish to Service, overwrite dataset.
In Power BI Service > Dataset Settings > Incremental refresh history,
Delete all partitions (this step is critical).
Trigger a full refresh in Service, this rebuilds schema without incremental logic.
Re-enable incremental refresh in Desktop, set RangeStart/RangeEnd, and publish again.
Run the refresh again in Service.
Hope this helps.
Thank you.