cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
CharlesS
Kudo Commander
Kudo Commander

Cannot import solution containing Dataflow (Error Code: 80040265, DataflowId already exists under a different environment)

Hello!

 

I am trying to import a simple unmanaged solution that contains four dataflows in a new environment. The purpose is to move the solution through ALM phases, from DEV to UAT to PROD. The solution import fails and I get the following message:

 

Error code
80040265
Exception message
Code: BadRequest Content: DataflowId already exists under a different environment

 

The error message is a little ironic... of course the Dataflow ID exists in a different environment, that's what ALM is all about.

 

I had previously been able to migrate dataflows between environments, no problem. Any idea what could be the cause?

 

Thanks!

 

Keep 'em flowin'

 

Charles

 

CharlesS_0-1653931685524.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
CharlesS
Kudo Commander
Kudo Commander

Hello All!

So I was able to solve my own problem.

 

Here are what I believe to be the possible causes of the problem (to Microsoft: these causes may be wrong! If they are, please reply to this thread to educate me and fellow community members):

1. The solution was imported into the environment by a user other than the owner of the dataflow.

2. Neither that user or the dataflow owner had an existing dataflow created in the target environment when the  solution was imported.

3. The dataflow was imported in the environment (shown in system Dataflow table), but left in limbo.

 

Number 3 above kinda explains the error message. There was a Dataflow with that name in the target environment (and in other environments), but I think that that the corrupted entry in the Dataflow table of the target environment was the problem.

 

This is how I corrected the issue:

1. Went in the Dataflow system table and deleted the corrupted rows (it says the table is read-only, but you can delete a row when you edit data in Excel)

2. Created a dummy dataflow, owned by the same user as the user of the dataflows in the solution I am trying to import. 

3. Created a new solution with the required dataflows.

4. Imported the solution as the same owner of the dataflows.

 

All good, dataflows are flowin!

 

Keep 'em 'flowin!

 

Charles

View solution in original post

2 REPLIES 2
CharlesS
Kudo Commander
Kudo Commander

Hello All!

So I was able to solve my own problem.

 

Here are what I believe to be the possible causes of the problem (to Microsoft: these causes may be wrong! If they are, please reply to this thread to educate me and fellow community members):

1. The solution was imported into the environment by a user other than the owner of the dataflow.

2. Neither that user or the dataflow owner had an existing dataflow created in the target environment when the  solution was imported.

3. The dataflow was imported in the environment (shown in system Dataflow table), but left in limbo.

 

Number 3 above kinda explains the error message. There was a Dataflow with that name in the target environment (and in other environments), but I think that that the corrupted entry in the Dataflow table of the target environment was the problem.

 

This is how I corrected the issue:

1. Went in the Dataflow system table and deleted the corrupted rows (it says the table is read-only, but you can delete a row when you edit data in Excel)

2. Created a dummy dataflow, owned by the same user as the user of the dataflows in the solution I am trying to import. 

3. Created a new solution with the required dataflows.

4. Imported the solution as the same owner of the dataflows.

 

All good, dataflows are flowin!

 

Keep 'em 'flowin!

 

Charles

Hi @CharlesS ,

 

Cheers! Please consider accept your reply as solution to help others find it.

 

Best regards,

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

Helpful resources

Announcements
Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on August 17, 2022 at 8am PDT.

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Users online (1,986)