Forum Discussion
'Alm_InvalidRequest_PurgeRequired' - Dataset xxx changes will cause data deletion
Hi dmkblesser ,
That error.
Alm_InvalidRequest_PurgeRequired – Dataset <name> changes will cause data deletion
basically means the deployment API has detected a schema change that would force the dataset to be dropped and fully reprocessed. A “purge required” scenario usually comes up in cases like:
- Column rename or removal (lineage breaks)
- Column data type change (incompatible with stored data)
- Incremental refresh / partition definition changes
- Changing or removing default date hierarchies (like the Auto date/time variation block you showed)
Adding new columns or measures is normally safe and won’t trigger it, but removing or altering existing ones almost always will.
In your case, disabling Auto date/time removed the default hierarchy metadata. Fabric sometimes treats this as a destructive change, which is why you see the purge-required error. What’s odd is that it only hit one of your 13 models, even though the same change was applied to all. That usually points to something unique about that model for example, existing partitions or relationships referencing the date hierarchy, which makes Fabric treat the change as breaking.
At this point you’ve got two paths.
- Allow the purge and force a full refresh after deployment (expected if the model really depends on that hierarchy).
- I’d recommend raising a support ticket with Microsoft so it’s officially logged and can help influence future improvements. You can do that here.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Regards,
Akhil.
Hi Anonymous. Thank you for your quick response.
When you say allow the purge and force a full refresh after deployment, how do I force the purge?
In the previous post, Rui and other community members suggest to either run the fabric-cli (we cannot use this option since we cannot modify the pipeline at this point) or use SSMS to run a refresh clear command.
I tried to use the SSMS option but it still doesn't work. Below is what I've done, please let me know if this is the same refresh clear command as mentioned in the post:
After I ran the process clear command, I can confirm that there is no data in the table but the deployment still failed to the same error message. (In this case, the model only contains one table)
thanks