Values of environment variables randomly change

(0) Share

Report

Posted on by Reinerknudsen87

We have several apps using environment variables which hold the connection information to the underlying SharePoint lists.

I have observed that we receive user complaints about error messages or data not loading. Most of these issues go back to the values in the environment variables being wrong. Sometimes the "list" field is empty, sometimes it contains a number (the list ID in SharePoint?). When I reset the variables to the correct value things work fine again - until next time.

Interestingly enough, it is never the environment variable for the site but always the list ones.

How can that happen? Is there some sort of log where I can see whether people go and change the values?

Categories:

Environment

All responses (4)

Answers (0)

Reinerknudsen87 59 on at

Like (0)

Report

Re: Values of environment variables randomly change

This is probably the most unsatisfying solution: Stay away from environment variables if you can.
No, we didn't find a solution. We also have no menas of investigating the issue any further. It just happens randomly.
kmansweden2017 20 on at

Like (0)

Report

Re: Values of environment variables randomly change

Same here, this happens all the time now during development (in dev env)
Havnt moved the soultionen yet.
Very frustrating.
CU03121049-0 15 on at

Like (0)

Report

Re: Values of environment variables randomly change

Hey @KarolZareba or @Reinerknudsen87 , have you been able to solve the issues you had? Were currently facing a similar issue in one of our environments.
KarolZareba 2 on at

Like (0)

Report

Re: Values of environment variables randomly change

I have been struggling with the same issue for a while. I am using environment variables to store SharePoint list IDs. The problem arises when I move the solution to a different environment and change the variable references to the Site and Lists while creating a new site for that specific environment. Periodically, errors occur where, for some reason, the environment variable reverts to the reference of the previous Site, causing production data to not be saved where it should or resulting in an error when searching for a resource by a specific ID, claiming that the record does not exist, which is obviously not true. However, the flow does not work because it is looking for the ID in the old list, which should not be present in the installed solution in a different environment. This is very weak and discouraging for further investment because it is not entirely stable.