Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

Deployment pipeline - Update on table set for incremental refresh

Hello,   I am using Deployment pipeline on a dataset which is using incremental refresh. I understand the limitations which are posted in the docs: Republishing a dataset that doesn't use increm...
Need Help
  • Nimrod_Shalit's avatar
    Nimrod_Shalit
    5 years ago

    We have the option to choose to continue the deployment,

    even if it means to drop the data.

     

    See more info here.

Anonymous's avatar
Anonymous
Not applicable
4 years ago

This is still an issue for us today. Has there been any resolution? It basically makes development with Incremental Refresh tables & Deployment Pipelines an impossible task.

Nimrod_Shalit's avatar
Nimrod_Shalit
Icon for Power BI Team rankPower BI Team
4 years ago

Anonymous can you explain what exactly is the problem?
there are many threads here so its hard to understand what problem you mean.

Also note that we do support incremental refresh, and also support deploying breaking changes by letting the user choose to continue the deployment and drop the data.

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    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.

    • RobinNeven's avatar
      RobinNeven
      Icon for Helper I rankHelper I
      4 years ago

      No response so far huh? We have the same issue...

      • Anonymous's avatar
        Anonymous
        Not applicable
        4 years ago

        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.