Unanswered

Deployment of power page as a solution

(0) Share

Report

Posted on by _Mayank

Hi Everyone,

I am using Enhanced data model of power page and adding site in a solution for migration from DEV instance to UAT and PROD,
and I am moving the solution as a managed solution.

After Deployment of solution in UAT instance, I've to change some code in it like power automate (HTTP Request) URL, Site URL for web API calling and some azure function url and client secret ID.

1- On changing of these url in managed solution it will create solution layer and affect our next deployment ?
2- Is is any better approach to make our deployment dynamic that we don't have to change these URL in Target Environment.

Thanks.

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (0)

Lucas001 2,529 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @_Mayank,

generally speaking, I would say it's the best approach using pipelines.
By depoying a new managed solution the old unmanaged layer is over written.
Have a look here: https://learn.microsoft.com/en-us/power-platform/alm/solution-layers-alm

I unfortunately haven't found a simpler solution for now. Any other tip is highly appreciated.

Was this reply helpful? Yes No
_Mayank 57 on at

Like (0)

Report
Copy link

Link copied!

Hi @Lucas001,
I always have to make changes in my code after the deployment of solution like power page site url, http request url, client id etc.
After changing all these code of line in manged solution it will create layer , is there any solution to avoid changes in code after deployment? Thats what I am asking.

Was this reply helpful? Yes No
Lucas001 2,529 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi @_Mayank,

no as the new deployment will always overwrite the last changes.
One approach we are currently checking are global variables. Within those you could store the link, url etc. as the environment variable can be set per environment, it's something what could work. But we are still testing it right now.

Was this reply helpful? Yes No
_Mayank 57 on at

Like (1)

Report
Copy link

Link copied!

Hi @Lucas001 ,
If you find any solution, please provide it.
Thanks!

Was this reply helpful? Yes No
Lucas001 2,529 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi @_Mayank ,

I reached out to the MVP Nicholas Hayduk and got a tip on how to do things.

Power Pages doesn't have any specific support for environment variables (i.e. there is no simple way to access them via Liquid or JS). Probably the most common way of doing it would be to use Site Settings. Create the site setting in each environment that has the correct value. Then ensure that the site setting is not part of the ALM process (so that it doesn't get overwritten from DEV). This will depending on what you're using for ALM. If using configuration migration tool, use fetchxml queries to ensure that site setting isn't included. If you're using the new enhanced data model and solution, ensure that the site setting isn't included in the solution. If you're using the PAC CLI, use deployment profiles (https://powerapps.microsoft.com/en-us/blog/power-apps-portals-create-deployment-profile-for-dev-test-prod-environment-using-power-apps-cli/).

--------------------------------------------------------------------------------------

Hope that helps.

If the post solves your problem, please mark it as solution. If it helps, consider a thumbs up.

Was this reply helpful? Yes No
_Mayank 57 on at

Like (0)

Report
Copy link

Link copied!

Thanks, @Lucas001 , for the solution!

I tried using Site Setting before, but it ended up getting included in my solution. Then, after deployment, I had to change those values, which caused issues with my solution.
I appreciate your suggestion, and I'll give it a try.

Was this reply helpful? Yes No
Lucas001 2,529 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @_Mayank,

did you achieve some results?

Was this reply helpful? Yes No