Data Source Environment Variables in Power Platform Solutions - SharePoint

[@edjk6278]

I remember seeing this a couple of years ago and not being able to fully grasp everything. Today I’m using this strategically. I used the video for a refresher… Thanks mate.

[@RezaDorrani]

Excellent! Thanks so much for the revisit.

[@gowrishankarg9922]

What will we do without your knowledge sessions like this? 🤔 .. Thanks, Reza, for this and for all your video sessions. Your service is so very valuable and very much appreciated.

[@RezaDorrani]

Thank You so much for liking and watching my videos.

[@aragondarupeshreddy]

From zero to hero in power apps developer with the help of Reza videos ❤️❤️❤️

[@RezaDorrani]

Thanks so much

[@ericzheng4838]

Each time I need to gain some PowerApps knowledge, Reza your channel is always my first choice!

[@RezaDorrani]

Thanks Eric!

[@danielrumbak2530]

I wish I had found this video earlier. Thank you Reza! Your service to us in the community is invaluable! Thank you again!

[@RezaDorrani]

Glad it was helpful!

[@filipesimoes2524]

Agree....much appreciated ! thanks Reza!

[@673ritesh]

Thanks for replying on video which was published 2 years ago.

[@RezaDorrani]

Thank You

[@SauloOliveira]

No words to describe the value of this video, thank you Reza for sharing your knowledge with us.

[@RezaDorrani]

Thanks Saulo

[@nihar4713]

this is brilliant , informative and much needed for me to get practical view of solutions and moving them across environments , very much appreciated!!!

[@RezaDorrani]

Great to hear!

[@sridharreddy1607]

Asusual amazing, you are the KINGPIN of Powerapps .....KUDOS

[@RezaDorrani]

Thank You so much Sridhar

[@notonurnelly]

Perfect timing Reza, I have been looking at Solutions and understand how they work for Dataverse Tables but was wondering how SP sites and lists work.

[@RezaDorrani]

These new data source variables make it easier to work with SP sites and lists

[@miryam5390]

Again Reza, your videos have been a time saver. Awesome work and thank you.

[@RezaDorrani]

Glad to hear it!

[@krowemoh76]

Reza, you are the man! Thanks for this super helpful video and for taking the time to share your knowledge.

[@RezaDorrani]

You are most welcome. Thank You for watching the video.

[@harithakumariphoghat6814]

Thank you so much sir🥰 really very informative and understanding. i was tired of searching for how to achieve this. Really thgank you so much

[@RezaDorrani]

You are most welcome

[@365g]

Many thanks for sharing... this is so powerful and makes life so much easier going forward 🙂

[@RezaDorrani]

Completed agreed. On the Power Apps community call next week, there is a lot more on environment variables - powerapps.microsoft.com/id-id/blog/may-19th-power-apps-community-call-multilingual-power-apps-environment-variables-and-more-environment-variables/

[@365g]

@@RezaDorrani Perfect cheers... Now in my calendar!

[@KamrulHasan-dz6vp]

Wonderful!! Thank you for sharing and updating us.

[@RezaDorrani]

You bet!

[@necdetsaritas8722]

Awesome. I have a lot of fun learning with you. Thanks Reza

[@RezaDorrani]

Happy to hear that!

[@bairikrishna0808]

You are awesome boss 😊 This is an advanced learning topic for me but great video, Thank you

[@RezaDorrani]

Glad to hear that! I try to include a mix of beginner and advanced topics to keep things interesting 😊

[@Leo_Russo]

This is really awesome! I was setting up the connections manually 😪

[@RezaDorrani]

It surely is awesome

[@sahilthakur03]

Thanks for sharing Reza. This has made me keen to explore how will the updates happen to say your App or flow, once you move your solution from say QA to Production.

[@RezaDorrani]

I feel every SharePoint and Power Platform related solution needs to use these variables going forward.

[@kalpeshpatil9]

Hi Reza, Thanks for the wonderful explanation about the ALM

[@RezaDorrani]

You’re most welcome

[@polrairfan]

Excellent Reza...thanks a lot for the video

[@RezaDorrani]

You are most welcome

[@gouravladha]

Thanks @Reza this is really helpful, I was really struggling with this issue as all apps were created in Production and have to migrate manually. Awesome :)

[@RezaDorrani]

You're very welcome!

[@adedaporh]

Great video Reza! What I currently do is to create a Choice column that represent the environments 😅. I will try this out and see which is better.

[@RezaDorrani]

Thanks for watching

[@joshhammz]

Hey Reza! At 13:00 you mention that we need to remove the Environment Variable site value before we export the Solution- will I need to add that value BACK in after I export the Solution so I can continue work on that development Solution? And is this is a step I need to take EACH time I export a Solution with Environment Variables? I've been doing a lot of learning and work with Solutions, Environments, and Pipelines and your videos have been immensely helpful, thanks for all the great content!

[@RezaDorrani]

No, once per env variable

[@SauloOliveira]

Valeu!

[@RezaDorrani]

Obrigado

[@vinothkumar7016]

perfectly explained. Thanks for the video..

[@RezaDorrani]

You're most welcome!

[@sujisam5508]

Thanks Reza 😊...This is very useful video

[@RezaDorrani]

My pleasure 😊

[@RudimarPowerApps]

You are the man!!! Great resource, thanks for sharing!! :)

[@RezaDorrani]

You bet!

[@johnnyongesa2246]

This is so valuable, thank you Reza

[@RezaDorrani]

Most welcome

[@raj7sam]

Very awesome feature Much needed. Thanks.👍🏼 Can you pls create detailed video for managed vs unmanaged? It will be helpful.

[@RezaDorrani]

Thank You. Managed vs Unmanaged is very well covered in the documentation - docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm#managed-and-unmanaged-solutions

[@praveenmanne3438]

Excellent video! Thank you for sharing

[@RezaDorrani]

Thank you Praveen

[@RavikiranS]

Wonderful video

[@RezaDorrani]

Thank You

[@isabellas616]

This is a great tutorial. Thank you!

[@RezaDorrani]

Your most welcome

[@bobbyw1074]

Thank u so much! Awesome content. Question, when creating a production sharepoint list(s), i believe the column names need to be the same. Is there an easy way to copy the test SP list to create a prod list or should i just manually create the new list and make sure the columns match?

[@RezaDorrani]

Column names and schema have to match. SharePoint has a concept of creating lists using JSON schema. I recommend checking SharePoint documentation

[@MrDionmar]

Tks a lot Reza !!!!! Just one question, every time that you bring some features from DEV to Prod environment, you need to compile the solution and import other time to production ???? The link URL to the App will always modified ? TKS so much!!!! 👏🏻

[@RezaDorrani]

Yes, you would need to export solution and import. It will keep app URL same in downstream environments. Give it a try and check.

[@juanversal47]

the best of the bests!!

[@RezaDorrani]

Thanks Juan!

[@canipeddi]

Hi Reza, When i am creating a flow with in a solution, I do not see an option to choose environment variables(step mentioned at 8:55) in sharepoint connector(when a new item is created), Is there any thing changed recently?

[@RezaDorrani]

You need to select custom item. Check in both new and old cloud flow designer.

[@canipeddi]

@@RezaDorrani I do not see an option to "Add a custome item", Instead i see "Enter custom value", when i choose it, there is no option for dynamic content , when i create the flow it starts with new designer but changes to old and do not see an option to switch it to new.

[@canipeddi]

Here is the image of what is see: drive.google.com/file/d/13iPklKkLcH8BLMRXNAkQGTZA2rgKOknR/view?usp=sharing

[@RezaDorrani]

I have not experienced this, hence not sure. I suggest posting your issue on forums community.powerplatform.com/

[@TheDistractionStudio]

Thank you! Amazing content.

[@RezaDorrani]

Glad you enjoyed it!

[@virajpatil6487]

Awesome, thanks for sharing 😊

[@RezaDorrani]

Thanks Viraj

[@sharepoint2936]

very well explained and problem solving video for soliution import export, but i have one question at 8:50. in flow i am unable add env variable, or unable to find parameter option. it sows custom value and cant fine env var in it.... pls explain stucked here

[@RezaDorrani]

Save flow. Edit again and see if it works. If still none shows up, then I would recommend posting your issue/query with screenshots on the forums at powerusers.microsoft.com

[@sharepoint2936]

@@RezaDorrani Thank u very much 👍 it works save & then try 👍👍👍👍

[@vijjureddy50]

Fantastic tutorial

[@RezaDorrani]

Thanks

[@coolbeing163]

Hi Reza, thanks for this video. v. useful. Few issues I am facing if you could suggest. I am not getting the option to add the Environment var (you shown in 8:40) in Power Automate. Do we need to enable any settings ? 2. As shown in step 12:21, Flow component didn't add their connection reference - Office Outlook and SharePoint. PS - I am using Trial environment.

[@RezaDorrani]

Seems weird. There is no setting as such.

[@coolbeing163]

@@RezaDorrani - Ok let me google once more time. thanks

[@siddharthgorowara3139]

Nicely explained

[@RezaDorrani]

Thank You

[@Usman_IBI]

Ah, long awaited feature.

[@RezaDorrani]

A true game changer for Power Platform projects with SharePoint as a data source

[@sainathp991]

Very nice .. it's very helpful.

[@RezaDorrani]

Glad it was helpful!

[@parwejp]

Nice! Smart solution to support non-native (non dynamics) components like power apps power automate. It was working well with CDS before. I remember that in some scenarios it doesn't allow you to add existing flows to solution previously. Hoping that it works for everything now. Do we need cds enabled environment for it? How will it work for power apps list form with multi environment support now ( another video on that) ? Thanks Reza for this one. 😊👍Crystal clear.

[@RezaDorrani]

Dataverse/CDS enabled environment is needed to work with solutions. Process of importing existing flows and apps to solutions has significantly improved. For SP customized list forms with Power Apps, I don't believe there are supported yet. For standalone Apps connected to SP Lists, this will work as demonstrated in the video.

[@parwejp]

@@RezaDorrani Thanks. Key ALM update announced does say that PowerApps list form will support ALM and multi environments. Roadmap is not clear. Could not imagine how but hoping environment variables will work for them as well. powerapps.microsoft.com/en-us/blog/key-alm-updates/

[@RezaDorrani]

I hope so too.

[@loishnr]

Awesome. Thank you. How would I handle running flows when I import an updated environment? Do I need self-recovering flows that will restart on every item and continue as needed?

[@RezaDorrani]

The flows that are in running mode will continue to use the previous flow schema. New flow runs will adhere to the updates pushed out via solutions.

[@MrDashingAshish]

Very well explained :) thanks for sharing

[@RezaDorrani]

Thanks Ashish

[@MrDashingAshish]

@@RezaDorrani recently I appeared for an power platform interview and in the end I mentioned your name to interviewer that I follow Reza :) and he was aware of you... :) you create nice content and have presentation skills. Keep up the good work 💪

[@RezaDorrani]

@@MrDashingAshish Wow. I feel it is all thanks to my subscribers who constantly share my content. I hope you cracked the interview 💪

[@RezaDorrani]

@@MrDashingAshish Congrats!

[@yoginathbadadale]

Thank you Reza 🙏

[@RezaDorrani]

Welcome!!

[@mtamitolanga]

Thank you Reza for this video much appreciated. SharePoint will have different sites for dev and prod, is the flow shared between dev and prod? If we only have prod, can we go back and create dev and qa then package the prod and push into qa and dev? Thank you.

[@RezaDorrani]

Check kzbin.info/www/bejne/jqCQhamQbrNmeK8 Flow is not shared. There will be 2 separate flows.

[@tetsuyakawahara4150]

Awesome!! Thank you😆✨

[@RezaDorrani]

Thanks Tetsuya

[@anthonyleduc]

What can i say on this video , except Wow. Migrate a powerapps to an another environnement will be no pain now

[@RezaDorrani]

Awesome!

[@dineshmunasinghe]

Thanks Raza!

[@RezaDorrani]

👍

[@Jaythang123321]

Thanks for this. I have come up with an issue on the Environment Variable name because the 'The length of the 'displayname' attribute of the 'environmentvariabledefinition' entity exceeded the maximum allowed length of '100'."}}'. The naming convention for the SharePoint site is managed by the customer. Is there a way to get around this limit?

[@RezaDorrani]

You can create the variable directly in solution and then connect it in App. Check kzbin.info/www/bejne/rnTKeqqGbKqIrZI

[@TondalayaLipshitz]

Brilliant

[@RezaDorrani]

Thanks

[@ThreeDigitIQ]

I cannot see any environment variables others have created and they cannot see or edit mine. Is there a way to share or change the owner of environment variables so everyone can use them?

[@RezaDorrani]

The step taken for environment variables prior to exporting is important (shown in video). I have not come across this issue and hence not sure what is the cause for your issue. I recommend posting your issue/query with screenshots on the forums at powerusers.microsoft.com

[@shreecanths]

Great video. I am having issues with Choice fields in PowerApps are not populating data though I set environment variable of the Prod environment. getting "The specified record was not found. Server Response: ListURL failed: List not found ". May be this could be bug from MS?

[@RezaDorrani]

This one is a known bug. Choice fields cause issues.

[@conaxlearn8566]

I noticed everytime you connect to a List, it creates one variable for Site and one variable for List. When you connect to multiple Lists in a Site, it still creates as many Site vairables as the List variables eventhough the Site value is same. Can we get rid of the redundant Site variables, Reza?

[@RezaDorrani]

When you try and connect to a new list, you do have an option now where you can select an existing environment variable. That way it does not create a duplicate. I think I showed it on the community call. kzbin.info/www/bejne/rnTKeqqGbKqIrZI

[@sharepointdeveloper602]

Thanks for amazing video. Nicely explained. I have one issue- not able to find environment variables in power automate. Even Add dynamic conent is not showing in trigger

[@RezaDorrani]

I will have to look at your flow in action to provide guidance. I would recommend posting your issue/query with screenshots on the forums at powerusers.microsoft.com

[@673ritesh]

Thanks for the video. I have one question. I have office 365 outlook connector added in my Powerapps app. This app is added in the solution. I was told to create connection reference for this but how do I use this connection reference in powerapps?

[@RezaDorrani]

It does so automatically learn.microsoft.com/en-us/power-apps/maker/data-platform/create-connection-reference

[@673ritesh]

@@RezaDorrani yes, it got automatically added when solution was imported in target environment. So I do not need to create connection reference for powerapps, right?

[@RezaDorrani]

@@673ritesh As long as you build in solutions, you don't have to do anything else

[@julien8979]

Thank you so much Reza for this great walkthrough on environment variables. I can understand if we used environment variables in the canvas app and we want to move the solution from dev to prod. it is not needed to re-add the datasource to the app and reconnect it to the form so it will avoid replacing datacards and we will not lose the datacards logic validations in the form right?

[@RezaDorrani]

In an ideal world Yes. But I have noticed some challenges with these environment variables.

[@conaxlearn8566]

Exactly what I need!!! Thanks Reza! By the way, how do you usually replicate SharePoint sites when setting them up for different environments?

[@RezaDorrani]

SharePoint Site Templates.

[@Abdulkhaleq-cb5sb]

Thanks Raza

[@RezaDorrani]

Always welcome

[@elenazakopniuk4224]

common knowledge, this is how we have been doing it for a long time.

[@RezaDorrani]

Very nice.

[@รถพรวนดินมิตซู]

Hi Reza, Can you advise, please? On the flow part, when you tried to add SharePoint site by clicking "+ Add a custom item" to pick parameters from dynamic content, I don't see the link of "Add a custom items" link under the Site Address. I already enabled "Experimental Features" under Settings of "View all Power Automate Settings". Thank you in advance.

[@RezaDorrani]

That is not an experimental feature. Add a custom site addresses is a standard feature of flow. Might be some bug in your environment. You may want to create a ticket with MSFT.

[@stevebekele4083]

Hi Reza, thank you for the great content you share. Is it possible to point environment variables to Document Library? My flow failed when I tried it.

[@RezaDorrani]

Should be possible but not something I have tried

[@stevebekele4083]

@@RezaDorrani, thank you. This is the error I am getting "Root folder is not found". When I put the library name instead, it works with no issue.

[@RezaDorrani]

@@stevebekele4083 Not sure. I will recommend posting your issue with screenshots on forums powerusers.microsoft.com/

[@nnylsnosrap]

I think I waited too long to do this! When I try to add my cloud flow and add the "when and Item is created", I don't see the option for dynamic content to be able to select the environment variables. Also when I add the cloud flow, though the "maker" environment looks like power automate, the url reflects powerapps (i notice yours at the time pointed to flow). Maybe I need a premium license to add flows to a solution and have all the environment variables? Im going to keep hunting but hoping you have an answer! Thank you for getting me all this way!

[@RezaDorrani]

Solutions requires Dataverse in environment, but user does not need to have premium license to create and use solutions. As for your issue, I recommend posting your issue/query with screenshots on the forums at powerusers.microsoft.com

[@nnylsnosrap]

@@RezaDorrani Thank you Reza! I heard from someone already that there is a known issue with triggers not working with environment variables. Either something has changed since a year ago when you posted this video or the issue is intermitent (only on some solutions). Im going to start over from scratch and see if the problem persists. Thanks for the prompt response!

[@lvimal2003]

Just a query, if we are using Site Data Source Environment variables, how the current user login will be taken for the Item Addition and Patching?

[@RezaDorrani]

Current logged in user logic would work as normal. No change there. User would need access to that SharePoint site.

[@andresgallegos3914]

Thank you so much for your videos. They are extremely helpful! Is there a way of doing this but with a SQL on prem data source instead of Sharepoint Lists?

[@RezaDorrani]

Currently, data source environment variables only support SharePoint.

[@chintandesai9942]

Awesome Reza once again. The explanation was clear and understood. thank you so much!!! If you can answer this. 8:41 I do not see the option to "Add a custom item". Do we need to activate any feature? Or Do we need extra permission at Security Role area?

[@RezaDorrani]

I have the experimental feature for flow turned ON. In your scenario, if you open list dropdown, at the end you will get the custom option.

[@sharepoint2936]

@@RezaDorrani unable to add parameter value or unable to select enviornment variable pls explain

[@RezaDorrani]

@@sharepoint2936 Cannot explain without looking at your issue in action. I will recommend posting your issue with screenshots on the forums at powerusers.microsoft.com

[@sharepoint2936]

@@RezaDorrani ok thanks I'll post on community

[@vksomething]

Could you help with a best practices video for a canvas app with SQL server as a data source. As environment variables are not supported for SQL Server by Power apps as on today, how do we manage SQL connections in QA and Prod.

[@RezaDorrani]

Sql is one of the data sources I have done least work on and have no plans on videos with Sql

[@kavyamuniswamappa]

Hi Reza, thanks much for your Knowledge sharing for all out there and me. Can we do this for SQL connection as well? I see only 3 choices, SharePoint, dataverse, sap ERP under data sources in env variable.

[@RezaDorrani]

I have not done any work with sql hence not sure. I will recommend checking on the forums at powerusers.microsoft.com/ in case someone has done something similar.

[@MsAmyrock]

Excellent Rena as usual!! Thank so much for sharing. I would like to know how to move solutions from one tenant to another. That is painful. Also, I wonder if there is a way to duplicate the SharePoint site and lists so I don’t have to create them manually in production when I’ve already created them in development.

[@RezaDorrani]

The process of moving solutions from one tenant to another is same as moving from one environment to another. To duplicate SharePoint sites and lists you would need to ensure that you create your lists via site designs feature in SPO. docs.microsoft.com/en-us/sharepoint/dev/declarative-customization/site-design-overview You can even trigger site designs using flow. Long ago I had written an article on this - rezadorrani.com/index.php/2019/01/14/invoking-unlimited-actions-with-site-design-tasks-and-microsoft-flow/

[@parwejp]

You can also make use of PnP provisioning templates. They work great if to be used by support team rather than end users. They are more powerful as well. For end users Site design make most sense.

[@RezaDorrani]

@@parwejp + 1 for PnP templates

[@MsAmyrock]

@@RezaDorrani thank you so much! I will look into this.

[@LAXMIKANT1992]

Very good informative video. I have a question - Suppose I imported the managed solution in my test or prod environment from Dev one. Now I have to change some component or add some customization to the app. So do I have to repeat the process again like first change it it dev then export it to test and prod or it will be visible to the environment automatically? 🤔

[@RezaDorrani]

You will need to make updates in dev and re-export. There are azure devops pipelines that help in automating this.

[@McIlravyInc]

How can I create an env variable (s) that I can use to update deep links in my flow emails?

[@RezaDorrani]

Video shows how to create environment variables for data source. You can create variable of type text as well and then use it in apps and flows. You can also check this video - kzbin.info/www/bejne/jqCQhamQbrNmeK8

[@issacong6280]

Hi Reza, I'm curious if we have deployed to another environment and we modify the original CDS table schema and redeploy to the same environment it will cause the error. How we can actually upgrade the table schema, for example one of the column is number type and we changed to text type.

[@RezaDorrani]

Il be honest, I have not done much with solutions. I will recommend checking on the forums at powerusers.microsoft.com/ in case someone has ran into a similar issue.

[@issacong6280]

@@RezaDorrani thanks for your quick response!!!

[@edjk6278]

While building flows in Power Automate will environment variables also be created by default? Or is this feature only available in power apps?

[@RezaDorrani]

Flows use connection references when built in solution context. I will recommend reading documentation on connection references.

[@tpcun024]

Thanks a lot for this video. I have a question for you if possible. Is it possible to create a variable for a Microsoft form id and use it ? My idea was to create a first step when a form is submited and a second one to get the details. I have created an environment variable in my solution with the form id but wasn't able to use it in the two steps (the environment variable isn't displayed)

[@RezaDorrani]

I have not tried this scenario but may be it is possible. I will recommend checking or posting your query on forums in case someone has done something similar powerusers.microsoft.com

[@malakabdelmoaty3736]

Thanks so much Reza for the amazing content you always produce, it is very much appreciated!! I had a question with regards to a specific scenario and that is having multiple projects and for each project we need to deploy an App and a set a flows every single time. The App will be exactly the same and flows do the same thing but just pointing to a different SharePoint site each time. Would it be possible to create a solution to act as a template in a DEV environment and then basically deploy that template in a PROD environment but each time with a different name and also get it to recreate the resources within the templated solution as new ones (i.e. App and flows)? Hope that makes sense and thanks again very much for all your incredible efforts.

[@RezaDorrani]

With SharePoint usage inside solutions, all you get is a reference to a data source. When you move from dev to test to prod, you would need to ensure your SharePoint sites and lists are all in place. You can automate that process through flow as well.

[@itsybitszy]

Awesome it's

[@RezaDorrani]

Thank you! Cheers!

[@TusharParekh]

Great Video! We used the same approach in our apps but after we export the solution and choose Sharepoint site and list from environment variables, it still somehow pulls data from old values. Not sure if this is a bug. Any idea?

[@TusharParekh]

I am mainly referring to choice fields :)

[@RezaDorrani]

Thank You. If referring to Choices function for Choice fields, then yes, it is a bug currently.

[@RezaDorrani]

It's a bug.

[@TusharParekh]

@@RezaDorrani Thanks for the reply. Good to know. I thought I was doing something wrong 😄

[@perrya3550]

Can you go in and modify the environment variable name afterward? It looks like it inherits the name of the datasource you use to create it initially? Small nitpick, but it'd be weird to have the env variable be called "ServiceDeskTest" in the production version of the solution. Also, very informative vid as usual. Thank you!

[@RezaDorrani]

You can modify it in the Solutions page. However, I have noticed that if you modify it, you will need to go back to your app or flow and re-associate. Not ideal. Im sure these small issues will be fixed soon.

[@akmamardzuan3655]

thank you for your amazing explanation I've try adding existing power automate flow into solution. but, the original flow in 'my flow' power automate was not there anymore. Thus, I copied back the flow and delete the solution. however, here come my problem. when I run the flow, it become redundant as run at two different places (my flow & solution). how can I turn off the flow in solution as it was not usable anymore?

[@RezaDorrani]

Within solution, when you go to cloud flows, you should have option to turn them on or off. I will have to look at your solution in action to provide further guidance. I would recommend posting your issue/query with screenshots on the forums at powerusers.microsoft.com

[@SilentInferno]

Hi Reza, we just have a single environment and I'm simply trying to point my app to a different SharePoint site and list. Basically I made a copy of the list for testing, built my app using that test copy, and now I want to point the app to the production version of the list. How can I do that?

[@RezaDorrani]

Simply change the environment variable to point to new list.

[@yogeshm8344]

HI. Great Work!. I have one doubt about Environment Variable Secrets. have one custom connector i am passing Secret Value in Text is not working. Or only that azure key vault is possible to passing a client secret

[@RezaDorrani]

AKV is the preferred option

[@yogeshm8344]

@@RezaDorrani any other option?

[@RezaDorrani]

@@yogeshm8344 I am not aware of any other option

[@akhilnadhpc]

The video is informative, But how can I move sharepoint list with its permissions also from dev to production env ?

[@RezaDorrani]

SharePoint sites are not environment specific. They are tenant specific. If you need another site with similar config and permissions, you would need to look into site designs, site scripts & PowerShell.

[@rezag.7349]

Wonderful presentation and highly needed feature. Thank you very much Reza. I have a question: when adding an Existing component e.g. app, how do I enforce the app to produce the Env. Vars? (Note: The app setting "Automatically create environment variables when adding data sources" was set to On and the app was republished consequently)

[@RezaDorrani]

You will need to remove existing data source connection & re-add. If even after app setting it is not showcasing the environment variable, then it may be a bug.

[@karthikeyans6787]

Hello Reza Dorrani, Thanks a lot for the helpful video sessions! I have a doubt, Is there a possibility to move APP and Power Automate Flows from One Environment to the Other Environment, That I want it to be only for the Developers. If So Whether the App and Flow will function which is already linked to data of existing sharepoint and environment ? TIA :)

[@RezaDorrani]

Welcome! Not sure I understand your question. Solutions can move apps and flows. Once moved to target environment, you can either connect to new site and list using environment variables or connect to existing ones without using it.

[@elliotavery6415]

Hi Reza, great video. Quick question... Do you need to be a global admin to run this?

[@RezaDorrani]

As long as you have environment maker access you should be able to work with this.

[@elliotavery6415]

@@RezaDorrani Many thanks

[@maitreyaroychoudhury9367]

Hi Reza, I had a question, I have observed when I am passing a sharepoint site and sharepoint doc library as environment variables in a excel online connector (in power automate), I keep on getting 'Bad Request' error (observed only in excel online connector, for sharepoint or any other connector it works fine), but static address works fine. Could you please let me know if there a workaround for this?

[@RezaDorrani]

Hi, I have not tried env variable with the excel online connector. I will recommend checking on the forums at powerusers.microsoft.com/ in case someone has done something similar.

[@uw1985]

Hey reza, again great video. Do you know if its possible to manipulate the environment variables from inside a app or a flow? Actual i use sharepoint list to store needed variables which i need in runtime of my apps or flows. But think it would great to use a environment variables for it cause i am able to use them in flows without a special initalize.

[@RezaDorrani]

I believe you need to update them from within the Solutions interface. Storing variables as env variables is a better option that SP list.

[@KavitaSingh-oc5ku]

Hi Reza I have only one environment in powerapp but my datasource has 3 different setup Dev, QA and Prod. I usually have to create 3 setup for this app but the link changes are hard to handle is there a better approach I can take? Need your advice...

[@RezaDorrani]

You would need multiple environments to truly take advantage of environment variables and ALM.

[@NavneetSingh-je9jp]

Thanks a lot for wonderful video Reza.. Your videos are awesome and very much detailed to help beginners as well. I see we can provide environment variables for power app and flows. I want to check if I customized SharePoint list form in power app. How can I deploy that form in production environment? Do we need to follow this solution and variable approach Or is there other way for the customized SharePoint list form?

[@RezaDorrani]

SharePoint customized list forms have a lot of limitations. One of them is the fact that they are only available in default environment.

[@NavneetSingh-je9jp]

@@RezaDorrani Thanks a lot for the clarification..

[@MrMytubejc]

Is it possible to import solution multiple times into production environment, giving each a unique name? I.e let’s say you had 3 service desk sites in your tenant and each wanted that same solution but linking to their sites/lists?

[@RezaDorrani]

Better option would be to have 3 environments in Power Apps. As you move from one env to another, you just need to update the env variable to the respective SharePoint site/list as shown in the video.

[@rahullko28]

Again Thanks was very useful, just wondering if we can use the environment variable within the Powerapps sendmailV2?

[@RezaDorrani]

Possible but currently reading environment variable in Power App requires querying Dataverse. kzbin.info/www/bejne/rnTKeqqGbKqIrZI

[@rahullko28]

@@RezaDorrani Sorry I should have mentioned earlier but that will require a premium license which I want to avoid.

[@RezaDorrani]

@@rahullko28 That is the only option for now. Better to use flow.

[@Lokesh.Singara]

What if I wanted to point to the same SP site and SP List, will it work without fail?

[@RezaDorrani]

Simply point your variables to the same site and list in that case. Why would it fail?

[@latifulkhan]

I have this error, what to do? The length of the 'displayname' attribute of the 'environmentvariabledefinition' entity exceeded the maximum allowed length of '100'.

[@RezaDorrani]

Looks like your SharePoint site URL must be a long one (exceeding 100 limit). I would recommend you build the environment variable first (and give it a name less than 100 characters) and then connect it in your Apps and flows. I did a demo of this on the Power Apps community call last week. Here is the link - kzbin.info/www/bejne/qKPHoZ6FiJ6jpM0

[@MrSardeshmukh]

Thanks Reza for such valuable video and knowledge sessions. Still environment variables can be used only for SharePoint as a data source?

[@RezaDorrani]

You can check and see :) I believe Yes

[@mardithpascua8112]

hi. i am working in a project. Canvass and SP as data repo. Do u have any tips guide? from maintaining SP list to managing app

[@RezaDorrani]

Nothing in the form of a video. Might be a good idea for a future video.

[@Lockerbille]

the BAD is you still need the solution or deploy dataverse for this. If you built app with only SP. Any update about if only use PA with SP?

[@RezaDorrani]

This concept works when one has multiple environments with Dataverse setup. Your tenant needs to have the capacity to setup environments. No premium licensing is needed for this feature.