I have a Solution with a canvas app and multiple flows. The solution initially has the Power Apps setting "add env vars when new data sources added" turned ON. Then I determined I will reuse one the SP lists rather than manage a DEV version and a PROD version so if there is a change, I wouldn't have to change it in two places.
So I updated the Power Apps setting "add env vars when new data sources added" to be turned OFF and I removed (not deleted) the env vars from the Solution. I tried to import it into my PROD env and I got the message shown below like it was expected env vars. Then I changed "add env vars when new data sources added" back to ON removed and added back data sources, exported Solution and tried again and I got the same dead end screen also shown below.
At this point, I'm not sure how to proceed to fix this import issue. Any recommendations are appreciated.
Glad it resolved your issue!
This resolved my issue as well. Thanks for passing along!
@nhurst05 - I resolved the issue by deleting the browser's cache. After relaunching a new browser window (post cache deletion) and importing the Solution again, I saw the updated screen shot below. I clicked the "review and adjust all connections" option to ON.
I reviewed the connections and clicked Next and the Solution successfully imported into my PROD env.
I hope this resolves your issue as well.
To provide a few additional details, I originally had Solution #1 which only used env vars for the data sources in the canvas Power App. I successfully exported the solution (DEV env) but as stated I could not import to the PROD env since the Import button was grayed out.
Next I removed all env vars from Solution #1 and updated the setting "add env vars when new data sources added" to OFF. Then I removed and added back my data sources (all SP lists). I successfully exported the Solution but I could not import to the PROD env since the Import button was grayed out.
So I decided to remove all flows and the one canvas app from Solution #1 and then I deleted it.
I created a brand new Solution, Solution #2 and added the canvas app and flows. I successfully exported the Solution #2 but I could not import to the PROD env since the Import button was grayed out.
So I have experiencing this issue with two Solutions. Perhaps it is a Microsoft bug/issue?
Thanks for your help! I will do the same if we figure it out.
Thank you. I will let you know if I get it resolved.
I have not. Still experiencing the inability to resolve the connection update requirement during the solution import.
@nhurst05 - Have you been able to resolve this issue? I'm not sure if it's a temporary issue but I'm not sure what action I can take to resolve this.
@SebS - Thank you for your response.
I stopped using env vars in my flows months ago after multiple instances of issues occurred and it was more trouble than it's worth. So my env vars are strictly used for the data sources in the canvas app.
Before exporting my solution, I always perform the "Add required objects" for the canvas app and the flows. This ensures all required connections are part of the solution.
No what I've tried today, with or without env vars I reach the dead end screen in my PROD env and the Solution cannot be imported since the Import button is grayed out. It's interesting another user, @nhurst05 is experiencing the same issue.
I just started getting the same dead end when trying to move a new solution to production. Before today, when moving a new solution into production, the import wizard would supply the needed information to tie the connection reference inside the solution to the connector in the environment. Now, it's just blank.