pbix files messed up after deployment in deployment pipeline

[Martin_D]

Hi,

I have following reproducible behaviour:

I have a deployment pipeline with stages DEV, QA, and PROD.

I publish pbix files from Power BI Desktop to DEV workspace and from there deploy to QA and PROD. 

From DEV to QA and from QA to PROD some deployment parameters are modified to load from different database environments. After each deployment, I also refresh the semantic model to get the data from the correct database environments and this works successfully.

Then, when I download a pbix file from PROD, I can download the file, and open it in Power BI Desktop, but the semantic model is messed up as shown below.

This is what I get in Power BI Desktop when I download a deployed report:

When I confirm to apply changes, this is what I get:

The semantic model becomes empty.

You can find examples of before and after files for your investigation attached.

Is this a bug, or is there anything I can do to download  reports that were deployed and have modified Power Query parameters properly?

Thank you very much!

Kind regard,
Martin

[v-shamiliv]

Hi @Martin_D 

That's great to hear that you're transitioning to DevOps integration to address this issue! If this solution resolves your problem,please mark it as solution. This will be helpful for other community members who have similar problems to solve it faster.

If you have any further questions or need additional help, please feel free to reach out to us.

Thank you!

[v-shamiliv]

Hi @Martin_D 
Thank you for reaching out microsoft fabric community forum.
Based on my analysis, it appears that the data types was not changed before moving it into production. Please try changing the data type before moving it, as this may resolve the issue.

I hope my answer helps you,if you need any further assistance, feel free to reach us.

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

Best regards,
shamili.v

[Martin_D]

Hi @v-shamiliv ,
Thank you for taking care of this issue.

What do you mean exactly by "data types" and by "changing before moving it into production"? The data types of the Power Query parameters or the columns or anything else? Deployment in Microsoft Power BI deployment pipelines never includes an implicit or explicit change data types step. Please describe what activity I need to do.

Actually everyting is typed in the original file, all Power Query parameters (it's only one) and all columns that are loaded into the data model, see screenshots below. The column datatypes are just inherited from the data source, and not applied explicitly in a separate Power Query step. Is this supposed by Microsoft to make a difference? Is that what you mean?

Kind regards,
Martin

[v-shamiliv]

Hi @Martin_D 
It appears to be clear on your side.To address your concern further, we kindly recommend raising a support ticket
The following link will guide you how to raise a support ticket, kindly refer to it.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

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

Best regards,
shamili.v

[Martin_D · Accepted solution]

Hi @v-shamiliv ,

The screenshots in Message 6 are from the original file before the deployment. There has never been an issue with this. Nothing is clear on my side. Anyway, we'll switch to DevOps integration to get rid of this problem.

Thank you!

Kind regards,

Martin

[GilbertQ]

Hi @Martin_D 

What happens if you don't click on applying the pending changes and go into power query? Can you still see all the information you need?

[Martin_D]

Hi @GilbertQ ,
That's a very good question! No, it's messed up. 0 queries:

Actually, that's why I was thinking about synchronizing the workspaces to a repo to open the files properly. But as you noticed in the other post, this also requires workarounds.

Best regrads,

Martin

[GilbertQ]

Hi @Martin_D 

I am not sure why that is happening to be honest.