Backend ErrorChanging the partition type from or to PartitionType.Calculated is not allowed

[CEllis]

Hope someone can advise me on this one.

I have added a parameter field and a new table to my application using PowerBi Desktop then published it to the cloud.

I then refreshed the new table and then the application.

I then went to deploy it to the the next stage using the pipeline deployment and go this error.

It has been working ok upto now.

Any suggestions greatly appreciated.

Many thanks

Chris

[danielvdm14]

I found the issue!

I deleted a calculated table and replaced it with a manual table using .

I gave the table the same name. I think that is what was causing the issue. The powerBI service didn't like that I changed a table from being a calculated table to a manual table. 

To fix it I juat gave the table a new name. That way powerBI saw it as a new table and not me trying to replace a table. 

[DeeceC]

legend! I owe you! this has saved me on a late night deploy. This should be the answer

[Anonymous · Accepted solution]

Hi, @CEllis 

In my tests, the three phases of the pipeline deployment function fine, as shown in the following image:

Based on the error your picture shows, did you change your semantic model and then deploy the pipeline? If you make changes to your semantic model during the tests phase, you may get an error. You can try republishing an already changed report to the new workspace and then deploying your pipeline to see if the three phases from DEV-TEST-PRODUCTION work to see if it works.

How to Get Your Question Answered Quickly

If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .

Best Regards

Jianpeng Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[CEllis]

Not sure this makes sence but.

I published to the workspace I cant deploy to (test) refreshed the sematic model(in test) then deployed again using the pipline (from design to test) and it works.

I am having the same problem at the next pipeline deployment from test to publish, i'll have a go at doing the same with that.