Data sources appear to be invalid after migration of an app from one environment to another

[Anonymous]

Hi everyone,

I have an app that I need to migrate from one environment to another.

I'm using the "Export package" option to export it and then "Import Canvas app" to migrate it to the other environment.

All the data sources already exist in the new environment before migrating the app.

But when I open the app, none of the data sources are recognized.

The Refresh button for the data sources don't do anything, the error remains.

The only way I can get rid of this error is to remove all the app data sources and add them back them again.

But for this app I have more than 20 data sources, so it takes a long time to add them back again.

We are often migrating the app, so I need to find a solution for this.

I have other apps that use most of these data sources, but they don't have any issue on migration.

Any advice will be appreciated.

Thanks a lot,
LS

[WarrenBelz]

Hi @Anonymous ,

When you say "the data sources already exist in the new environment", are they the same or copies of them in a different location?

I suspect they are copies, which means the only way to do the transition is to delete and re-connect as you have. 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[Anonymous]

Hi @WarrenBelz,

The data sources were already created in the new environment long before the migration of the app. I mean the SQL tables and views that I’m using in the app.

So, there was no reason for the app to show that invalid data sources errors.

I also tried to migrate the app on another environment (the third one). I had the same error and I had to deleted and create the data sources again.

Thank you,

LS

[WarrenBelz]

Hi @Anonymous ,

What I meant is this the same SQL data source as you were using on the test app? I migrate between (Power Apps) environments all the time and never have an issue with data as long as you specify the connection in the import wizard. Am I missing something?

[Anonymous]

Hi @WarrenBelz,

Yes, the SQL data sources are the same in the 3 environments. The data sources should be recognized after migration, because they have the same name.

I wonder why it happens this, because I have other apps that use the same data sources and can be migrated without any issue.

Thank you,
LS

[WarrenBelz]

Hi @Anonymous ,

You have actually answered my question in that they are not the same. Power Apps references more than the name in the background and cannot find the one it was connected to, hence you need to reconnect (so what you are experiencing is to be expected).

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[Anonymous]

Hi @WarrenBelz,

The Database, tables and views names are the same. The only thing that is different is the environment name (instead of Stage, I'm using Dev).
But I'm selecting them during the import, as the connections are already created.

Other apps works after migrating them, without re-creating the data source.
But this one is different.

Thank you,
Luminita

[WarrenBelz]

@Anonymous ,

So I understand you correct, are they one or two SQL data sets and are they referenced exactly the same?

[Anonymous]

Hi @WarrenBelz,

I have one flow and 2 Databases that I'm using. I use about 20 tables and views from these databases.

I'm selecting the equivalent of the Databases during the import:

After selecting the equivalent sources:

Thank you,
LS

[WarrenBelz]

@Anonymous ,

I am only trying to put some logic around what you are experiencing - I do not believe I can offer any advice to change it.

I am a SharePoint user and I know that when I change from Test to Prod data sources, I need to re-connect all relevant tables as Power Apps references these with parameters beyond the table and field names and field types. Conversely, if I maintain the same data sources (as I do with all reference tables), I do not have to reconnect them.

I will tag one of my colleagues @Anonymous , who may have more insight into this.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.