PowerApp name in different environment with solution imports and exports

(0) Share

Report

Posted on by KrishR

431

Hello Power Users,

I was building a canvas app, lets say "DemoApp". While moving the package from one environment to another I would like to have different name to it. Like when it is migrated or imported to UAT, want to call the app DemoApp UAT. It would be possible to rename it. But I would do this import and export multiple times in a day and would be hard to rename always before and after the import and export.

Is there a way that I can achieve this functionality where I would have different name in different environment that would make my task easier and also my testing team to know the app they are testing is in UAT.

Can anyone please help me or suggest if any approach for this?

Thanks in advance!

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Kuhlani 82 on at

Like (0)

Report

Hi @KrishR

I would suggest not changing the name and instead using a dynamic way to show in a small label on the top (left or right) what stage of the lifecycle the app is. Here is a suggested way:

Create a flow that can pull the current environment GUID then run it through a switch control to validate:
Cases:
GUID = development environment, return "DEV"
GUID = UAT environment, return "UAT"
Default case is blank. so that if you push the app to any production environment, it will return nothing.

You can run the flow OnStart to get the label with the right tag dynamically and never worry about it in the future.

The value in that your checking against in the switch statement is an expression:

workflow().tags.environmentName

I hope you find this useful.

Was this reply helpful? Yes No
Snoemannen 32 on at

Like (0)

Report

I'm also looking for a solution for this, and have yet to find a good solution.
I have built an app that is getting deployed to several different administrations with their own environment.
But some people have access to more than one of these environment.
So when they are looking for the app on their mobile phone they will see several apps with the same name.
The environment name is visible below the name but it is still very confusing for the users.

The "workaround" we do now is to just change names manually in each environment, but it is quite a tedious task that is prone to errors since you have to remember to remove the unmanaged layer and then change name every time you deploy a new version.

Was this reply helpful? Yes No
SimonSays 168 on at

Like (0)

Report

I'd love to find a cleaner way to do this also!

Was this reply helpful? Yes No