Forum Discussion
Power BI Service - Source Control with Azure DevOps
Hey everyone,
I'm having some problems lately trying to deploy changes to my dataset from Visual Studio Code and Azure DevOps.
The last error message I got is the following one:
Alm_InvalidRequest_PurgeRequired, do you know what it means?
Thanks in advance!
Regards,
Alicia.
5 Replies
Hi alicialcaide ,
I have not encountered a similar error report before, you can try the steps to check:
- Is there a conflict between the local version of your dataset and the one that is currently deployed in the Power BI service.
If so, you may need to perform a "Purge" operation to remove the conflicting dataset from the service, and then redeploy your changes.
- Is there not enough space available in the database to complete the operation.
- Checking the available disk space in the database and ensuring that Autogrow is turned on. You may also want to consider dropping any indexes or tables that are no longer needed to free up disk space.
If it does not help, please provide more details with the error.
Best Regards
Community Support Team _ RongtieIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello,
so I just encountered this error as well, the only google hit landed me here and I was able to solve it by doing the following:
- deleting the problematic dataset from the service (but not commiting!)
- reverting that change
- then hitting update all
Really weird error and very weird workaround. Hope this helps for anyone else!
Please note: This will make your deployment pipeline loose its bindings!
To keep the bindings you need to use XMLA and use the refresh: ClearValues Script to remove the underlying data in the dataset. See here for a in-depth solution:
Hi alicialcaide , Did you find a solution for this error?
I am getting the same error and as Anonymous mentioned to check for conflicts. I checked and there's no conflict. However, I couldn't understand steps you mentioned Anonymous to check for enough disk space. In my changes, i changed format of my date columns from Integer to Date format. Would that have increased the size of the dataset?Also, I tried syncing the branch in another workspace, which synced without any error.
Thank you
Hey Parthlad,
It happened the same to me, there was no conflict in my commit but there was a conflict on Power BI Workspace, that I couldn't find. What I did, was to look for the oldest version of my file that I knew it was working perfectly and download it, to replace it in the local folder sync with Azure DevOps repo. Then, I did the whole process again: create branch, publish branch, stage changes, commit and then, merge into main. And, when I did that, I was able to deploy everything on Power BI Service without any problem.
The only thing was that I had to develop again a couple of changes I made, but it was not a big deal.
Hope it helps!
Alicia
Hi alicialcaide ,
I had to do the same. I rolled back to previous commit for which it was syncing without any error. Luckily i had stashed it before i pushed my changes to remote. So i wouldn't have to redo it.
I was looking into conflicts where i connected my Power BI Service dataset and local Power BI Desktop file using ALM Toolkit and found some differences with Incremental Refresh tables.
Anyways thanks for your reply.
