cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
mattbell
Advocate II
Advocate II

Data Source Environment Variables not working for combo boxes based on SharePoint

Hi
I have migrated a solution between environments.  The solution includes an app whose data is based on a SharePoint library.  There are some combo boxes in a form which were automatically created from the choice fields in the SharePoint datasource.

When I import the solution I update the datasource EV to the correct SharePoint site.  This works correctly in the app apart from on the combo boxes.  I need to delete and re-connecting the datasource and that fixes it.  A refresh doesn't work, and re-connecting the data source using the EV works.

A bit of a nuisance because I obviously don't want to touch the app in the destination environment.

Anyone else experienced this and knows a fix?

 

Thanks

Matt

28 REPLIES 28

Hence why I posted this.  Now you have a choice - wait an unspecified amount of time for the bug to be fixed, or use my workaround.

dave-jorgensen
Kudo Collector
Kudo Collector

Ah. You stated in the initial post "I obviously don't want to touch the app in the destination environment", but as you've discovered, that is the only way around the bug.

capoaus75
Advocate II
Advocate II

This issue seems to have been resolved on my tenancy.

 

Also there was an issue with "Allow searching" in combo box. If the option was ON, when the solution was imported to a new environment the "Allow searching" option was OFF in the imported canvas app.  From my tests this issue has been resolved as well.  Definitely few steps in the right direction for ALM. Well done Microsoft!!!

For me the connection references update fine in the Canvas App but not environment variables. I have imported solution with the Power Platform CLI using the available commands to generate a settings file, defining all connection reference Ids and Environment variables definitions. The problem is in the canvas apps the data sources and instant flows hold broken references to older environment variable values. I have to manually delete them and then re-add them based on the new environment variables definitions.

 

What region is your tenancy? I am in the United Kingdom region so is it possible this feature hasn't been fixed in my region yet?

dave-jorgensen
Kudo Collector
Kudo Collector

As of last time I checked:

PowerApps - data source environment variables used in app don't update if the variable is changed after deploy

Power Automate - data source environment variables in flow update successfully if the variable is changed after deploy

NOTE: for the environment variables to reflect the change in flows, after you change the variable value you need to turn off and then turn on the flow. Values used in flow will continue to be the old value until you do.

I am also experiencing an issue with the Environment Variables - i.e. they don't work at all!

 

I've not yet even got to the stage of deploying a solution from DEV to PROD, but I am already experiencing an issue with the Environment Variables in the DEV environment.

 

I have an EV for connection to a SharePoint Document Library - I wanted the option to easily change between a "Documents_DEV" and "Documents_PROD" Document Library (both in the same SharePoint Site).

I created the EV successfully, and when in the PowerApps Studio - the Datasource is indeed pointing to the  list selected in the "Current Value".

However, when I "Play" the published app - it uses the list in the "Default Value", and not the "Current Value".

So, it doesn't even do what it is supposed to do as a basic function (i.e. be a lookup for what value to use)...

 

... and why have a feature that performs differently in the Studio than it does when Published?

Makes no Sense!

 

James.

Quick update on the above...

... I can confirm that the "Published" App also completely ignores the List selected in the "Default Value"...

It seems that the app just decides to connect to a Document Library of its own choice.

 

BOTH the "Current Value" and the "Default Value" are set to the "Documents_DEV" Library, yet when the App is played in published mode, the App points to the "Documents_PROD" Library, 

 

So, my development/test system seems to be permanently connected to my PROD Document Library, EVEN WHEN THERE IS NO REFERENCE TO THAT LIBRARY.

 

This is a Huge Security and Data Integrity FAIL, and can potentially cause DISASTERS!

 

So here's my advice:

DO NOT USE ENVIRONMENT VARIABLES - THEY CAN PERMANENTLY SCREW UP YOUR DATA SOURCES.

 

James.

 

This may be a daft question but something which I didn't find very obvious.  Did you connect the data sources using the Advanced tab when connecting to the SharePoint library?

Also, don't use the default values when creating EVs.  They do have a purpose but not one I have come across yet

Hi @matt_bellster ,

 

Yes - I did indeed connect to the datasource using the advanced tab... (and I clicked advanced to get to the "EV's" rather than select a list)

 

The most worrying thing is that my app is looking at one datasource when in the Studio, but a different datasource when published...

(and the datasource that the published app is looking at isn't even referenced at all - either in the App OR the environment variable)

 

James.

Default values have a very specific purpose - they just don't work with datasource environment variables. The way it works for everything else is, you set a default value in your DEV environment. You, in all practicality, don't EVER want to create a Current Value in your development environment. When you deploy into your target environment, you set the CURRENT value there (and in practicality never change the default value there).

Power Platform uses Current value if it exists else it uses the Default value (with everything other than data sources, which are just plain broken / buggy in PowerApps but fine in Power Automate).

The idea then is, when you do subsequent deployments, since there is no Current Value in your solution it doesn't overwrite the Current Value in the target environment and therefore they "persist" for that environment. It's why you never want a Current Value in your DEV environment (and it would be great if that was disabled, to prevent users from doing it), because if you have a Current Value in your solution then that gets deployed to target and overwrites the Environment-specific value. That defeats the whole purpose of environment variables, if you deploy / overwrite the Current Value.

Helpful resources

Announcements

Power Platform Connections - Episode 7 | March 30, 2023

Episode Seven of Power Platform Connections sees David Warner and Hugo Bernier talk to Dian Taylor, alongside the latest news, product reviews, and community blogs.     Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show.     

Announcing | Super Users - 2023 Season 1

Super Users – 2023 Season 1    We are excited to kick off the Power Users Super User Program for 2023 - Season 1.  The Power Platform Super Users have done an amazing job in keeping the Power Platform communities helpful, accurate and responsive. We would like to send these amazing folks a big THANK YOU for their efforts.      Super User Season 1 | Contributions July 1, 2022 – December 31, 2022  Super User Season 2 | Contributions January 1, 2023 – June 30, 2023    Curious what a Super User is? Super Users are especially active community members who are eager to help others with their community questions. There are 2 Super User seasons in a year, and we monitor the community for new potential Super Users at the end of each season. Super Users are recognized in the community with both a rank name and icon next to their username, and a seasonal badge on their profile.    Power Apps  Power Automate  Power Virtual Agents  Power Pages  Pstork1*  Pstork1*  Pstork1*  OliverRodrigues  BCBuizer  Expiscornovus*  Expiscornovus*  ragavanrajan  AhmedSalih  grantjenkins  renatoromao    Mira_Ghaly*  Mira_Ghaly*      Sundeep_Malik*  Sundeep_Malik*      SudeepGhatakNZ*  SudeepGhatakNZ*      StretchFredrik*  StretchFredrik*      365-Assist*  365-Assist*      cha_cha  ekarim2020      timl  Hardesh15      iAm_ManCat  annajhaveri      SebS  Rhiassuring      LaurensM  abm      TheRobRush  Ankesh_49      WiZey  lbendlin      Nogueira1306  Kaif_Siddique      victorcp  RobElliott      dpoggemann  srduval      SBax  CFernandes      Roverandom  schwibach      Akser  CraigStewart      PowerRanger  MichaelAnnis      subsguts  David_MA      EricRegnier  edgonzales      zmansuri  GeorgiosG      ChrisPiasecki  ryule      AmDev  fchopo      phipps0218  tom_riha      theapurva  takolota     Akash17  momlo     BCLS776  Shuvam-rpa     rampprakash  ScottShearer     Rusk  ChristianAbata     cchannon  Koen5     a33ik   Heartholme     AaronKnox        Matren        Alex_10        Jeff_Thorpe        poweractivate        Ramole        DianaBirkelbach        DavidZoon        AJ_Z        PriyankaGeethik        BrianS        StalinPonnusamy        HamidBee        CNT        Anonymous_Hippo        Anchov        KeithAtherton        alaabitar        Tolu_Victor        KRider        sperry1625        IPC_ahaas      zuurg    rubin_boer   cwebb365   Dorrinda   G1124   Gabibalaban   Manan-Malhotra   jcfDaniel   WarrenBelz   Waegemma      If an * is at the end of a user's name this means they are a Multi Super User, in more than one community. Please note this is not the final list, as we are pending a few acceptances.  Once they are received the list will be updated. 

Microsoft Power Platform Conference | Registration Open | Oct. 3-5 2023

We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5 2023! But first, let's take a look back at some fun moments and the best community in tech from MPPC 2022 in Orlando, Florida.   Featuring guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, Stephen Siciliano, Hugo Bernier and many more.   Register today: https://www.powerplatformconf.com/   

Check out the new Power Platform Communities Front Door Experience!

We are excited to share the ‘Power Platform Communities Front Door’ experience with you!   Front Door brings together content from all the Power Platform communities into a single place for our community members, customers and low-code, no-code enthusiasts to learn, share and engage with peers, advocates, community program managers and our product team members. There are a host of features and new capabilities now available on Power Platform Communities Front Door to make content more discoverable for all power product community users which includes ForumsUser GroupsEventsCommunity highlightsCommunity by numbersLinks to all communities Users can see top discussions from across all the Power Platform communities and easily navigate to the latest or trending posts for further interaction. Additionally, they can filter to individual products as well.       Users can filter and browse the user group events from all power platform products with feature parity to existing community user group experience and added filtering capabilities.     Users can now explore user groups on the Power Platform Front Door landing page with capability to view all products in Power Platform.    Explore Power Platform Communities Front Door today. Visit Power Platform Community Front door to easily navigate to the different product communities, view a roll up of user groups, events and forums.

Welcome to the Power Apps Community

Welcome! Congratulations on joining the Microsoft Power Apps community! You are now a part of a vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun! Now that you are a member, you can enjoy the following resources:   The Microsoft Power Apps Community Forums If you are looking for support with any part of Microsoft Power Apps, our forums are the place to go. They are titled "Get Help with Microsoft Power Apps " and there you will find thousands of technical professionals with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Apps community forums! Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered!   Microsoft Power Apps IdeasDo you have an idea to improve the Microsoft Power Apps experience, or a feature request for future product updates? Then the "Power Apps Ideas" section is where you can contribute your suggestions and vote for ideas posted by other community members. We constantly look to the most voted Ideas when planning updates, so your suggestions and votes will always make a difference.   Community Blog & NewsOver the years, more than 600 Power Apps Community Blog Articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on building Power Apps. On the Power Apps Community Blog, read the latest Power Apps related posts from our community blog authors around the world. Let us know if you would like to become an author and contribute your own writing — everything Power Apps related is welcome!   Power Apps Samples, Learning and Videos GalleriesOur galleries have a little bit of everything to do with Power Apps. Our galleries are great for finding inspiration for your next app or component. You can view, comment and kudo the apps and component gallery to see what others have created! Or share Power Apps that you have created with other Power Apps enthusiasts. Along with all of that awesome content, there is the Power Apps Community Video & MBAS gallery where you can watch tutorials and demos by Microsoft staff, partners, and community gurus in our community video gallery.   Again, we are excited to welcome you to the Microsoft Power Apps community family! Whether you are brand new to the world of process automation or you are a seasoned Power Apps veteran. Our goal is to shape the community to be your ‘go to’ for support, networking, education, inspiration and encouragement as we enjoy this adventure together!   Let us know in the Community Feedback if you have any questions or comments about your community experience.To learn more about the community and your account be sure to visit our Community Support Area boards to learn more! We look forward to seeing you in the Power Apps Community!The Power Apps Team

Users online (3,959)