Unanswered

Distribution of the development environment via Pipeline

(0) Share

Report

Posted on by SamLele

I created a Pipeline to deploy my solution (including the App) from the development environment to the production environment.

After the first deployment, I open PROD and see my solution, but when I make further changes within the app in my DEV environment and try to redeploy it, these changes are not reflected. I am forced to delete the solution and reload it.

However, I noticed that if I create a new table in DEV and deploy it, this change is reflected. I only have this problem with changes to the canvas app.

Can you advise me on a solution?

Categories:

Governance & administering

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

Pstork1 68,707 Most Valuable Professional on at

Like (1)

Report

Did you make any changes to the app in production? If you did it created an unmanaged layer that supersedes the managed layer in the solution. You can read about that here: Solution layers in Power Platform - Power Apps | Microsoft Learn

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
AlbertoCastro 1,201 Most Valuable Professional on at

Like (0)

Report

have you published your app before deploying?

Was this reply helpful? Yes No
SamLele 20 on at

Like (0)

Report

@AlbertoCastro Yes, before distributing public always all customizations

Was this reply helpful? Yes No
SamLele 20 on at

Like (0)

Report

@Pstork1 No changes are made in the DEV and then published

Was this reply helpful? Yes No
SamLele 20 on at

Like (0)

Report

@Pstork1

Actually I had a higher level in my solution, especially on the app in PROD.
In particular: I opened the solution in PROD > right click on the app > Advanced > See solution levels.
Here I found a second record that was blocking the update and I deleted it thus solving the problem.
Thank you very much for your help.

Was this reply helpful? Yes No