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.

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.

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?

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

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (5,006)