Unanswered

Model Driven App (MDA) - Error moving Solution between Environments - DataFlow Reference issue

(2) Share

Report

Posted on by Erikpgh1

I have created an MDA Solution that uses Dataflow to import some Data. Within our DEV environment we have Created and deleted a number of dataflows, However we are now getting an error message below when I try to move the Soltuion from one environment to the Next (DEV -> TEST).

When I try to import into the new Environment the Log shows the below error.

EntityRelationship [xxxxxxxxx_offersconsol_ProfitCenterRef_cr0e0_p_zprofitcenter] is invalid. The lookup attribute [xxxxxxxx_ProfitCenterRef] is already associated with an existing relationship.

While trying to search for any reference to the offending Table, Dataflow, and form fields, which was " Deleted" from the environment. I did find some of my lingering dataflows references in the below system Dataflow table (READ ONLY).

Does Anyone have any guidance to eliminate the reference or assist with the error code above or next steps to correcting the error so I can import my solution to the next environment. Thanks in Advance.

FYI..Decent How to of Dataflows into a Solution; How To Create Power Apps DataFlows? | Power Apps (devoworx.net) and MS Create and use dataflows in Power Apps - Power Apps | Microsoft Learn

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Sort by

BhargavPatel 660 Moderator on at

Like (0)

Report
Copy link

Link copied!

I know someone who recently had issue importing solution with Dataflows.

Here are few things to try:

1. In the Dev environment remove all the Dataflows from solution (do not delete them from the environment).

2. Then try importing the solution to the Test environment.

3. If you are able to import the solution after removing all the Dataflows form the solution, create a new Dataflow (do not make a copy of the old Dataflow) in the solution in Dev environment.

4. Trying importing the solution with new Dataflow to the Test environment.

5. If you are able to successfully perform step 4, then that tell you will have to re-create all the original Dataflows in the Dev environment.

Was this reply helpful? Yes No
Erikpgh1 44 on at

Like (0)

Report
Copy link

Link copied!

Found the Answer:

Removed all references to the offending dataflow within the forms, and data and the Table....

Now the trick, within the solution navigate to "Schedule" .... if the dataflow has a scheduled refresh, then there will be a reference left that does not get deleted.

As a whole it took some time to find all the associated references.

Plus following some of these directions from BhargavPatel (thanks)

1. In the Dev environment remove all the Dataflows from solution (do not delete them from the environment).

2. Then try importing the solution to the Test environment.

3. If you are able to import the solution after removing all the Dataflows form the solution, create a new Dataflow (do not make a copy of the old Dataflow) in the solution in Dev environment.

4. Trying importing the solution with new Dataflow to the Test environment.

5. If you are able to successfully perform step 4, then that tell you will have to re-create all the original Dataflows in the Dev environment.

Was this reply helpful? Yes No
Erikpgh1 44 on at

Like (0)

Report
Copy link

Link copied!

Is there any way to really get rid of lingering dataflows. Most of these are no longer in the Solution or the Environment.

Was this reply helpful? Yes No