microsoft / microsoft/Analysis-Services

LRO API Error: 'Alm_InvalidRequest_PurgeRequired'

Open
#338 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
732
Forks
433
PR merge metrics
No merged PRs in 30d

Description

Getting below error when deploying the reports to powerbi workspace where we are modifying schema of table/column.

LRO API Error: 'Alm_InvalidRequest_PurgeRequired' - Dataset 1f0b0ea6-a781-4392-9dbe-5e4c346e77af changes will cause data deletion.
At C:\PowerShellModules\FabricPS-PBIP\FabricPS-PBIP.psm1:283 char:13
+             throw $message
+             ~~~~~~~~~~~~~~
+ CategoryInfo          : OperationStopped: (LRO API Error: 'Alm…ause data deletion.:String) [], RuntimeException
+ FullyQualifiedErrorId : LRO API Error: 'Alm_InvalidRequest_PurgeRequired' - Dataset 1f0b0ea6-a781-4392-9dbe-5e4c346e77af changes will cause data deletion.
##[error]PowerShell exited with code '1'

Can you suggest here how we can resolve the issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the deployment failure at FabricPS-PBIP.psm1 line 283 and identify how the LRO API reports schema changes that may delete dataset data. Review the deployment and dataset schema documentation for the required purge behavior. Done means establishing a reproducible resolution or documenting the exact deployment steps needed for this error.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api, data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.