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.

james_hathaway
Advocate V
Advocate V

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

james_hathaway
Advocate V
Advocate V

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

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

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. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!      

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Community Roundup: A Look Back at Our Last 10 Tuesday Tips

As we continue to grow and learn together, it's important to reflect on the valuable insights we've shared. For today's #TuesdayTip, we're excited to take a moment to look back at the last 10 tips we've shared in case you missed any or want to revisit them. Thanks for your incredible support for this series--we're so glad it was able to help so many of you navigate your community experience!   Getting Started in the Community An overview of everything you need to know about navigating the community on one page!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Ranks and YOU Have you ever wondered how your fellow community members ascend the ranks within our community? We explain everything about ranks and how to achieve points so you can climb up in the rankings! Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Powering Up Your Community Profile Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile. Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Blogs--A Great Place to Start There's so much you'll discover in the Community Blogs, and we hope you'll check them out today!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Unlocking Community Achievements and Earning Badges Across the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. Check out some details on Community badges--and find out more in the detailed link at the end of the article! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Blogging in the Community Interested in blogging? Everything you need to know on writing blogs in our four communities! Get started blogging across the Power Platform communities today! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Subscriptions & Notifications We don't want you to miss a thing in the community! Read all about how to subscribe to sections of our forums and how to setup your notifications! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Getting Started with Private Messages & Macros Do you want to enhance your communication in the Community and streamline your interactions? One of the best ways to do this is to ensure you are using Private Messaging--and the ever-handy macros that are available to you as a Community member! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Community User Groups Learn everything about being part of, starting, or leading a User Group in the Power Platform Community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Update Your Community Profile Today! Keep your community profile up to date which is essential for staying connected and engaged with the community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Thank you for being an integral part of our journey.   Here's to many more Tuesday Tips as we pave the way for a brighter, more connected future! As always, watch the News & Announcements for the next set of tips, coming soon!

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Users online (2,496)