cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

Pick Environment variable based on current environment

The reason we use Environment specific values is that application should automatically detect the current environment and take the appropriate values. If these are just configuration values which in general all developers use, I don't see any value addon

 

I Suggest since multiple values are possible for a variable ; A Environment record (OrgName) should be created and against it the values should be created and once deployed the values should be read from destination orgname. This way it removes the overhead of verifying the values in each environment post deployment .

for eg :
Orgurl ->
devorg: https://devorg.crm.dynamics.com
sitorg : https://sitorg.crm.dynamics.com
prodorg: https://prodorg.crm.dynamics.com

 

This might be an addition to Get environment ID within Flow or app 

Status: New