Answered

"Next" button is disabled when import solution to new environment

(4) Share

Report

Posted on by hongkong

277

I am transferring my solution (with canvas app, automate flows, environment variables, connection reference) from dev and test environment.

There is an existing solution in Test environment. So I delete the existing solution then try to import a new one.

As the screenshot below. There is no error at all. But I am not able to press Next:

It is not first time we import solution. However, there was NO SQL server environment variable defined in my previous experience although we have SQL datasources long time ago. I am not sure why Microsoft auto create those variables now. But it seems a problem.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (2)

CU14021349-0 3 on at

Like (0)

Report

Could you find a solution? I have the same problem.

Was this reply helpful? Yes No
NicholasFirman 3 on at

Like (0)

Report

I am also experiencing this issue. It says there is one more connection with 'updates needed' than is shown. I haven't added a new a connection but it is acting like there is a connection that needs an update but it is not giving the option to update it.

Was this reply helpful? Yes No
Verified answer

Ravindra Jadhav 342 Moderator on at

Like (0)

Report

it's seems to an issue, you can report it

Please Closed the Question, Mark it Solved

If my answer helped resolve your issue, please consider marking it as solved to assist others facing the same problem. Additionally, giving it a like would be greatly appreciated and motivates us to keep helping

Thank You

Ravindra Jadhav

Please Subscribe to https://www.youtube.com/@jadhav_ravi_oo7

Connect On https://www.linkedin.com/in/ravindra-jadhav-powerplatform/

Was this reply helpful? Yes No
Verified answer

hongkong 277 on at

Like (0)

Report

The problem is fixed after I deleted the App and rebuild from scratch. This time no SQL connection reference is created. I am able to import solution to another environment as usual. My tips: don't use SQL connection reference and variables

I have also reported the issue but the support reach me after I rebuild the App. After some checking with support, we confirmed the missing environment variable is gone. Since my problem is resolved we did not spend more time for troubleshooting.

Was this reply helpful? Yes No