Unanswered

New AppID when updating solution?

(0) Share

Report

Posted on by JimmyW

2,563

I have a solution that uses deeplinking to a powerapps in emails.
The deeplink contains the URL of the application with the AppID and some variables.

I have the one DEV enviroment, unmanaged solution and one PROD enviroment managed solutions.

I make the changes I need ion DEV export it as managed and move it to PROD.

Will an update or upgrade always change the AppID, as this breaks my deeplinking in emails, they will now point to an app that does no longer exists.

I maybe should have thought the deeplinking part thru more, but is it correct that each time i make an update, export from dev to prod, I will get a new AppID? And if yes, how can I solve this with still using deeplinks to to point to the correct app?

Categories:

Governance & administering

I have the same question (0)

All responses (6)

Answers (1)

joe_hannes_col 1,843 Super User 2024 Season 1 on at

Like (1)

Report

Hello @JimmyWork,

As long as you update the solution in the Prod environment, the app ID will not change. Your deeplinks are going to continue to work.
You might still consider using environment variables for your links, as you will be able to change the app ID in an environment variable more easily than if you have hardcoded it in your app (if you're not doing this already): https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables

Was this reply helpful? Yes No
JimmyW 2,563 on at

Like (0)

Report

Thank you for answering. @joe_hannes_col
I'm using environmental variables, nothing is hardcoded.

But I develop in DEV, unmanaged solution.
The I publish to PROD as managed solution.

What you are saying I should develop in PROD? Because once I update a solution from DEV to PROD a new ID is generated.

Would you say this is the correct approach for PowerApps, and DEV, UAT, PROD environments are basically one? Then why package it as solutions? have 2 solutions for each one dev and one prod, will just be a messy clutter?

Was this reply helpful? Yes No
joe_hannes_col 1,843 Super User 2024 Season 1 on at

Like (2)

Report
Hello @JimmyWork,

Sorry, developing in Prod is not what I meant at all. Developing in a Dev environment and then pushing the solution to Prod (with intermediate steps like UAT, if applicable) is absolutely the correct approach.
What I was trying to say is:
You start developing a solution in Dev, and add a Canvas App to your solution.
You then import this solution into Prod. When you first import the Canvas App inside the solution, an app ID is generated for this app in Prod.
When you make changes to your solution in Dev, and then import the updated solution into Prod, the app ID will not change. Your links will continue to work (as long as you do not overwrite the environment variable values in Prod with the ones from Dev, that is).

Was this reply helpful? Yes No
JimmyW 2,563 on at

Like (0)

Report

@joe_hannes_col Thank you for clarifying.
However if I use environmental variables based on App ID would they not need to be updated when moving from DEV to PROD

Was this reply helpful? Yes No
Verified answer

joe_hannes_col 1,843 Super User 2024 Season 1 on at

Like (1)

Report

Hello @JimmyWork,
The environment variable(s) would have to be set to the app ID in Dev for the DEV environment, and to the app ID in Prod for the PROD environment.
So after you first imported your app to PROD as part of your solution, you will have to retrieve the PROD app ID, and then you will have to update the environment variable with this PROD app ID. If you haven't already, please review the limitations on environment variables, for example, you might have to turn off and then turn on flows that use your environment variable to enforce the new value.

Was this reply helpful? Yes No
JimmyW 2,563 on at

Like (0)

Report

@joe_hannes_col Thank you for taking your time and answering me.

Was this reply helpful? Yes No