Forum Discussion
Deployment pipeline - Update on table set for incremental refresh
We have the option to choose to continue the deployment,
even if it means to drop the data.
See more info here.
After a few seconds I've determined that the error message is inaccurate / a red herring - which is always frustrating for a user. The loss of data (even when there is none) is not an issue. It appears the way to solve it (at least for me), is to remove the Incremental Refresh config on the table and publish. That at least allows for a successful deployment and for the column name to change. Later, I guess we need to reapply the Incremental Refresh configs. All very frustrating for this month's release!
Obviously, the error message isn't necessary if devs allowed the renaming when no records exist in the tables.
Nice workaround, but jeez, that's super annoying and shouldn't be necesary. I have dozens of incremental refresh tables each with highly customized policies, its unrealistic for me to toggle them on and off just to deploy with the pipeline. I've been just publishing the dataset directly to the upstream workspaces, then circling back to the deployment pipeline in order to invoke my custom deployment parameters, then refreshing the dataset and carrying on with life.
I've gone through an entire ticket cycle on this with Microsoft and have been told its still an issue. Here's the most recent quote from my support tech:
"After circling internally, I figured that we still don’t support this action for Incremental Refresh datasets and tables unfortunately. Apologies for the confusion.
Our engineering team is working now to see how we can add this support for future cases; however we don’t have an ETA yet."
Please make it happen, Microsoft. You're our only hope.