cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
BenAu
Helper I
Helper I

Environment variables premium or standard

Hi,

 

I have tried searching but have been unable to find much information regarding the licensing around the the use of environment variables.

 

A google search brings up https://powerusers.microsoft.com/t5/Building-Power-Apps/Environment-Variable-Licensing-in-Canvas-App... which says they are most likely a standard inclusion.

 

When I add one to a solution and try use it in an app but adding the environment variable connectors, the app becomes a premium app. Is there any concrete information on the licensing of this feature?

 

Thanks

Ben

1 ACCEPTED SOLUTION

Accepted Solutions
RusselThomas
Community Champion
Community Champion

Hi @BenAu ,

This conversation was got me curious - it's not something I've really ever had to do, so I decided to spend a few minutes actually looking at this and I think I've found a solution.

Initial testing seems to indicate you can get Power Automate to help the app know what environment it's in, simply by triggering the flow - without using any maker or CDS connectors.

If you create a PowerApps triggered flow as part of your solution, you can pull out the headers from the PowerApp trigger - from there you can suck out the app id, the environment id and more.

  1. Create a PowerApps triggered flow
  2. Add a compose step but just set it to something arbitrary - "hello world" is fine.  Save the flow, connect your app to it, then trigger it from your app.
  3. Open the flow run, expand the PowerApps trigger and select "show Raw outputs" - copy everything you see there.  Note key fields like "x-ms-client-tenant-id", "x-ms-client-environment-id" and other potentially useful fields like user id and name - but for now just copy the whole lot.

Now, you can decide how best to do this bit, but for illustration purposes;

  1. Remove the compose step, replace it with a Parse JSON step
  2. In the Content field of the Parse JSON, add the expression triggerOutputs()
  3. Paste everything you copied into the sample schema for the JSON step.
  4. You can now see and access the data quite nicely in the JSON construct for your next step.
  5. Create a "respond to PowerApps" step and pass back the environment ID (and anything else you need). 

 

Your app should be able to use this to lookup environment specific variables, and the flow it uses should package with your solution and move through environments with it.

Let me know how it goes! ‌‌

Kind regards,

RT

 

 

View solution in original post

12 REPLIES 12
RusselThomas
Community Champion
Community Champion

Hi @BenAu ,

So first thing is, this is a 'best guess' answer - we would have to ask the product team to give an official answer, but I'm fairly certain we can guess closely what it will be. 

Secondly - preview services can (and most will) change before going into general availability.  There are few guarantees and plenty of disclaimers when it comes to preview services.

Lastly, "using CDS" and "using the CDS connector" are two different things.  While Approvals use CDS tables, the Approvals connector is not a premium connector. 

Environment Variables are a Common Data Service (now Dataverse) entity accessed by using the CDS Connector which, from my experience anyway, is premium.  

Unless you're building your app in a Teams Dataverse environment (which is not premium), or you use something else to store your env variables, if you're using a Common Data Service connector to access data in the Common Data Service (Dataverse), it will make your app premium. 

CDS/Dataverse common environment variables are very useful if you're using CDS, Solutions and/or some level of devOps between environments, but if all you want to use are common variables centralised somewhere, there are easier and cheaper ways to do it.

Personally, I prefer to use a simple SPO list to store common variables anyway, because a list as a data source is not locked into an environment and as such, variables can be standardised across environments or localised for specific environments by adding an environment id field - all without touching CDS/Dataverse.

Hope this helps,

RT

BenAu
Helper I
Helper I

Hi Russel,


Appreciate the detailed response.

 

The app we are building is a canvas app with flows using SPO as the data source.

 

I was experimenting with env variables to make maintaining the app between a dev/staging/prod environment easier as the flows and app have some links/functions that need to change per environment.

I wanted to be able to:

  • Import the dev app into another environment
  • Set an environment variable at the solution level without having to edit the app or flows
  • Have hard coded functionality in the app and flows to respond to what the environment variable is set to

 

Pretty simple stuff.

 

Would love to just store data in SPO for this, but I see no way to make the app or flows aware of what environment they exist in, any ideas?

 

Thanks
Ben

RusselThomas
Community Champion
Community Champion

Hi @BenAu ,

So that's really the primary reason env variables in CDS are useful (and sometimes necessary).  Self-aware apps are tricky inside the app - there are apparently plans to improve this with additional actions/functions, but what, where and when this might be possible is anyone's guess.  SPO only really helps for global variables across environments - localising for environments using the id field is also only useful if you're using the Makers connector - which helps for some "admin-only" app functions, but not for general user variables.   

I generally use SPO centralisation for things like email headers, adaptive card content or other commonly used components that I want to edit in one place and have all apps that use them auto-update.  Tying them back to the specific environment the app finds itself in for user functions is very difficult (if not downright impossible at the moment). 

The problem as I'm sure you're aware is that apps are not self aware - the environment container is a static boundary that can be accessed using "current environment" context which is dynamic - and this way each environment can carry variables accessible to solutions inside it without the solutions themselves needing to know what environment they're in.

The Makers connectors will allow you to pull app properties in-app, which include the current environment name/guid the app is running in, but the problems is this only works for app owners.  Pointless for users running an app and wanting to fetch variables specific to the the app environment.

So yes, if you need user-accessible variables that are different for each environment, you're kinda stuck with environment variables.  Happy to be corrected, but that's my experience.

Kind regards,

RT 

RusselThomas
Community Champion
Community Champion

Hi @BenAu ,

This conversation was got me curious - it's not something I've really ever had to do, so I decided to spend a few minutes actually looking at this and I think I've found a solution.

Initial testing seems to indicate you can get Power Automate to help the app know what environment it's in, simply by triggering the flow - without using any maker or CDS connectors.

If you create a PowerApps triggered flow as part of your solution, you can pull out the headers from the PowerApp trigger - from there you can suck out the app id, the environment id and more.

  1. Create a PowerApps triggered flow
  2. Add a compose step but just set it to something arbitrary - "hello world" is fine.  Save the flow, connect your app to it, then trigger it from your app.
  3. Open the flow run, expand the PowerApps trigger and select "show Raw outputs" - copy everything you see there.  Note key fields like "x-ms-client-tenant-id", "x-ms-client-environment-id" and other potentially useful fields like user id and name - but for now just copy the whole lot.

Now, you can decide how best to do this bit, but for illustration purposes;

  1. Remove the compose step, replace it with a Parse JSON step
  2. In the Content field of the Parse JSON, add the expression triggerOutputs()
  3. Paste everything you copied into the sample schema for the JSON step.
  4. You can now see and access the data quite nicely in the JSON construct for your next step.
  5. Create a "respond to PowerApps" step and pass back the environment ID (and anything else you need). 

 

Your app should be able to use this to lookup environment specific variables, and the flow it uses should package with your solution and move through environments with it.

Let me know how it goes! ‌‌

Kind regards,

RT

 

 

BenAu
Helper I
Helper I

Hi Russel,

 

Not sure what I am doing wrong 🙂 

 

I can see the app and tenant ID's when looking at the output of the PowerApps trigger as per you post above.

I can add the output the to generate sample parse json action, what I can't do is pass the output of the trigger to the content of the parse json action.

 

Within the parse json I see:

BenAu_0-1614557673245.png

 

If I select the Ask in PowerApps content, it automatically changes it to the ParseJson content so its referencing itself and not the output of the trigger causing it to error.

 

BenAu_1-1614557748086.png

 

My flow:

 

BenAu_2-1614557826496.png


Thanks
Ben

 

Hi @BenAu ,

Apologies, forgot to add that bit - will edit the post for future users.

We don't need to ask PA anything as we're just using the trigger outputs.

First, delete and recreate your PowerApps trigger if you've added any PA inputs.  Then, in the Parse JSON content field, use the following expression;

triggerOutputs()

In PA, you can add the flow to a button and just set it's OnSelect: property to something like

Set(gvarPAOutputs, flowrunName())

Let me know how it goes,

RT

Hi Russel,

 

So I can get this working on our dev environment. The flow simply runs in the app on start which will allow me to hardcode links based on the environment value.

 

My issues are now with moving the solution into other environments 😞

 

I have added the powerapps triggered flow to my solution, when I export the solution and import it into our staging environment I can see the flow has came across fine but within the connections inside the canvas app the linked flow is now white indicating the connection is no longer connected to the flow.

 

Have I missed a step here or will it just be that we have to re-connect the instant flows when moving a solution around?


Thanks

Ben

RusselThomas
Community Champion
Community Champion

Hi @BenAu ,

In my experience, connections inside apps always have to be "recreated" or reconnected in new environments because the connection is set to whatever GUID the connection instance was for the old environment.    

Sometimes the solution import process tries to reconnect flow connections for you automatically, based on their names, but I've never seen it do app connections automatically...  Open to correction, but I would expect you need to reconnect with each environment move...

Kind regards,

RT 

BenAu
Helper I
Helper I

Hi Russel,

 

Finally got the time to respond.


Have managed to implement this and bring our app into production and would like to write what I did in case others come across this.

 

Our application is part of a solution across three environments, we have a single data source being SharePoint which is used by all three environments at the moment.

 

Within the canvas app we are identifying the environment the app runs in as per your above instructions. This value is then used within the app to set some hard coded links etc.

 

The app also uses the value when saving records back to SharePoint which now has a column called Environment within its lists. So depending on what environment you run the app in the data being saved will actually record that environment.

 

This environment value is then used for any flows that trigger on values in SharePoint. On each environment we modify the trigger conditions of the flow to only trigger if the environment value in the SharePoint data is the correct environment that flow exists in. This means if a flow exists in all three environments it will not run when data is added to SharePoint unless the data meets the environment condition added to the trigger.


Next steps will be to get the flows to identify what environment they are in themselves but a quick check of the SharePoint trigger conditions doesn't appear to show any environment information.

 

The process of moving changes between environments does have manual steps but its manageable. 

 

Appreciate the prior assistance.
Ben

 

 

Helpful resources

Announcements

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Our team will be reviewing posts using the new "Copilot" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!      

Tuesday Tips: Getting Started in the Community

TUESDAY TIPS is back!   This weekly series of posts is our way of sharing helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! The original run of Tuesday Tips was a highlight of last year, and these all-new Tips will hopefully prove to be just as informative as helpful. We will cover some basics about the Community, a few "insider tips" to make your experience even better, and sharing best practices gleaned from our most active community members and Super Users. Make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   THIS WEEK: I'm Brand New! What Do I Do? The number of new community members we have each week is pretty amazing, and we are so glad to welcome all of you to the Community! You may be wondering. "What do I do? Where do I get started? Will anyone be willing to help me? What I have a question? Help!"   Let's start with this: Welcome to the low-code revolution, and more importantly, welcome to the Power Platform Community! This is a great place to start. Whether you're busy with Power Apps, getting familiar with Power Automate, engaging Copilot Studio, or building in Power Pages, there are a few key places you should check out as you begin your journey: FORUMS: The forums are THE place to ask questions, look at questions asked by other Community members—and see answers and solutions from our Super Users and other helpful people in the Community. Power Apps ForumsPower Automate ForumsCopilot Studio ForumsPower Pages Forums   NEWS & ANNOUNCEMENTS: Our News & Announcements section highlights the newest and greatest updates in the Community, news from the product team, and so much more. It’s updated a few times each week and will also help you find ways to connect with what’s going on in the ever-growing world of Power Platform. Power Apps News & AnnouncementsPower Automate News & AnnouncementsCopilot Studio News & AnnouncementsPower Pages News & Announcements   GALLERIES: The Galleries section of the Community features tons of tips and tricks, features and benefits, and more—through videos created by our Super Users, product teams, and other helpful members of the Community. Power Apps GalleriesPower Automate Galleries Copilot Studio GalleriesPower Pages Galleries BLOGS: The community blogs section is full of handy step-by-step tips from members of the Community—and some of them include detailed answers to some of the questions most frequently asked questions, as well as how they solved a problem they faced. Power Apps Community BlogPower Automate Community BlogCopilot Studio Community BlogPower Pages Community Blog POWER UP PROGRAM: If you’d like to really take a huge step forward in your journey, we recommend checking out the Power Up Program, a Microsoft-sponsored initiative that trains new Power Platform users and has been a huge success since it launched a little over a year ago. There’s a waiting list, so definitely apply soon if you’re interested! Find out more here: Microsoft Power Up Program for career switchers.   There's so much more you'll discover in your Power Platform experience, and this Community is here for YOU! We are glad you've discovered us and can't wait to see where you grow! If you're new to the Community and just getting started, make sure to give this post a kudo and introduce yourself so we can welcome you!

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

February 2024 User Group Update: Welcoming New Groups and Highlighting Upcoming Events

It's a new month and a brand-new year, which means another opportunity to celebrate our amazing User Groups!Each month, we highlight the new User Groups that have joined the community. It's been a busy season for new groups, because we are thrilled to welcome 15 New User Groups! Take a look at the list below, shared by the different community categories. If your group is listed here, give this post a kudo so we can celebrate with you!   We love our User Groups and the difference they make in the lives of our Community! Thank you to all the new User Groups, new User Group leaders--we look forward to hearing about your successes and the impact you will leave!   In addition to our monthly New User Group spotlight, it's a great time to share some of the latest events happening in our User Group community! Take a look at the list below to find one that fits your schedule and need! There's a great combination of in-person and virtual events to choose from. It's a great time of year to connect and engage with User Groups both locally and online. Please Welcome Our NEW User Groups   Power Platform: Heathcare Power Platform User Group Power Platform Connect Hub Power Platform Usergroup Denmark Mexico Norte- Power Platform User Group Pune Power User Group Sudbury Power Platform User GroupMicrosoft User Group GhanaMPPBLR - Microsoft Power Platform Bengaluru User Group Power Apps:   Myrtle Beach Power Platform User GroupAnanseTechWB PowerApps Copilot Studio: Pathfinders Power Platform Community Dynamics365: Cairo, Egypt MSD 365 Business Central/NAV/F&O User GruopMS Dynamics 365 Business Central LatamCincinnati OH D365 F&O User Group February User Group Events February 2024 Cleveland Power Platform User GroupPortallunsj - Februar 2024Indiana D365/AX February User Group MeetingQ1 2024 KC Power Platform and Dynamics 365 CRM Users Group 

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Top Solution Authors
Top Kudoed Authors
Users online (5,327)