I have an app that uses environment variables to reference a SharePoint site and a list on that site. This app is developed in a Dev environment and then exported to a Prod environment in a managed solution. I need some help understanding how changing the value of the environment variables in the production environment will impact the app in the managed solution.
These are the steps I followed and the behavior I have observed:
- Exported solution (managed) from the dev environment with the current and default values of the site and list variables set as blank.
- Imported the solution into the prod environment. During the import process I was prompted to provide values for both Site and List variables. These were set to the production assets
- Verified that the app correctly referenced the production assets
- In the Default Solution in the production environment, I changed the current value of the site and list variables to reference the development assets
- Verified that the default values were still blank
- Opened the app for edit in the default solution and verified that it now referenced the development assets
So far this is as I would expect. Next I did this:
- "Played" the app in the default solution - it still referenced the production assets
- "Played" the app in the managed solution - it also still referenced the production assets
I have verified that the latest version of the app is the published version and I have tried restarting my browser session but still can't get the apps to correctly reference the development sites when played. I am totally baffled by this behavior and would like some help understanding what is happening and how to change environment variables so that they impact managed solutions as expected.

Report
All responses (
Answers (