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.
Absolutely, thanks for reaching out Nimrod_Shalit. I think what I'm looking for is how to enable what you say "letting the user choose to continue the deployment and drop the data" because I don't seem to have that option. The popup message I get doesn't have the option to proceed:
How do I bypass this error/warning and push the deployment through, knowing and understanding (and wanting) to rebuild all incremental partitions? Is there an admin setting or toggle I'm missing somewhere? For instance, its very common for us to add new columns to our incrementally refreshed fact tables, warranting a full reload in these instances.
No response so far huh? We have the same issue...
Yes, still an issue for us as well. Nimrod_Shalit can you help us out? We're still not getting the option to continue deployment even if it results in data loss, its not an option in the popup pasted in my original message.
RobinNeven our annoying workaround is simply to manually publish the PBIX forward to each workspace, update our deployment pipeline parameters manually (for Dev/Test server names and date filters in our case) then trigger a full refresh (incremental tables get rebuilt). Very lame and time consuming, especially since we have numerous huge fact tables that get rebuilt and typically we'd only need to update one at a time if we could actually use the pipeline properly.