Unanswered

"Bad Data Source" error after deploying onto other environment

(1) Share

Report

Posted on by ipogoretsky

Hi! Having troubles after deploying canvas app (with Azure SQL connector data sources) onto different environment (with different Azure SQL connector having cloned database).

Deployed app "doesn't see" data sources.

On refresing any data source having an error:

{

status: 400,

message: Bad Data Source\r\n inner exception. Not a valid data source,

...

}

Removing-and-adding the same data sources solves a problem.

Additionaly founded out that on importing app, all its advanced settings are reset to defaults...

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

v-monli-msft on at

Like (1)

Report

Hi @ipogoretsky ,

See in below documentation:

https://docs.microsoft.com/en-us/power-platform/admin/environment-and-tenant-migration

If an app depends on a connection (such as a SQL connection w/ credentials), we do not currently support exporting the connection or credentials as a part of the package.

If you have an app that relies on a shared connection (like SQL), your only current option is to manually re-create that connection with the appropriate credentials in your target environment and select that connection when you import the package.

Regards,

Mona

Was this reply helpful? Yes No
ipogoretsky 10 on at

Like (0)

Report

I know all steps of deploying procedure. Many times did it. The propblem I described appeared a couple days ago. I choose connector from the list and after get an error. All credencials are ok. Seems to be a bug of powerapp deployment process

Was this reply helpful? Yes No
ipogoretsky 10 on at

Like (2)

Report

Founded out that issue was caused by app settings flag "Enable Enhanced Micosoft SQL Connector".
Turning it off solved a problem.

Was this reply helpful? Yes No
Pasark 20 on at

Like (0)

Report

I had the same issue. After exporting the app, recreating the SQL Connector, importing the app, I couldn't get the data from SQL. Disabling Enable Enhanced Microsoft SQL Connector solved the issue.

Was this reply helpful? Yes No