You’re offline. This is a read only version of the page.
Announcements
636
For a "quick win", I configured a flow within a solution hosted in the Development environment to use an environment variable created in another solution ( which has its deployment delayed), which is available in the advanced tab of the dynamic data picker. This is great, until I attempt to import the current solution into the Production environment, as it is picked up as a missing dependency. Note, I am trying keep a common set of environment variables to be used in all solutions e.g. for common lists or support information.
So to resolve this, do I simply recreate the environment variable in the current solution , and or remove it from the solution that is yet to deployed - this one was manually added , not auto created?
Update: just tried to recreate the variable without removing the current one in the other solution, I guess this further illustrates my dilemma .
Doh! just realised I am being a dumb ass. 🙄all I need to do is import the existing environment variable , keep calm and carry on!
Share
Report
All responses (
Answers (
