Solution import clears values from SharePoint List environment variables

(1) Share

Report

Posted on by RobHardy

154

I have a Power Platform solution which uses 14 SharePoint list. The lists are set using Data source environment variables, allowing dev, UAT and Prod versions to connect to different sites and lists.

Previously, when exporting a solution package from my dev environment for import to UAT / Prod, I would make sure that I had removed the current value of the env vars from the solution before export. On importing an upgraded version of a solution package, any values which had already been set in that environment would be retained (and only changeable through the Default Solution).

This has now changed. Instead of an option to remove the current value from the env vars in the solution package, there is a new "Export Value" setting for each (which I have disabled in my unmanaged solution), and on import there is an option to change the value which has already been set.

However, I am finding that the List (data source) variables are being unset every time I import a new version, and I have to set the value again.

This is complicating the upgrade process, and increasing the risk of error and disruption to users.

Has anyone else experienced this? And is there a solution?

Thanks,
Rob.

Categories:

Connecting to Data

All responses (3)

Answers (0)

RobHardy 154 on at

Like (0)

Report

Solution import clears values from SharePoint List environment variables

@FLMike

I did encounter a cross-dependency issue during the upgrade which meant I had to remove and re-create the solution in the production environment. However, connections are showing for the lists in both environments. It doesn't match the connection in the dev environment, in the sense that the dev environment uses my account to connect, while prod uses a service user, but this has been the case since I first created the solution.

If this is the issue, is there a fix that you're aware of? It does seem to be a regression.

@SpongYe

Column names are the same in the lists. Exporting the values of the list env vars from dev defeats the point of using them for the connections, though, so far as I can see it. The point of using them is that the app needs to connect to different data sources in dev and prod, and the list values are stored as GUIDs, which will be different in each site, not as the name of the list,
Suggested answer

Michael E. Gernaey 40,720 Super User 2025 Season 1 on at

Like (0)

Report

Solution import clears values from SharePoint List environment variables

Hi

The only time I ever saw this, is if the Connection itself was exported clear, or if someone recreated it.

Does the Connection that is IN that environment still exist and does it match what the Connection is defined in the Project?

Any chance someone accidentally removed it? Which would have messed it up like this, even if they put it back?
Suggested answer

SpongYe 5,580 Super User 2025 Season 1 on at

Like (0)

Report
Solution import clears values from SharePoint List environment variables

Hi,

I just runned a quick test on my side and it looks like it working for me.

Please make check the Current limitations:

To successfully use environment variables with SharePoint lists, the display name and the logical name for each corresponding column in the source and target environments must match.

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/EnvironmentVariables#current-limitations

My DEV env:

Target Enviroment