I had a similar challenge when I imported a solution with dataflows to the target env. These dataflows were then automatically copied by the system from the solution to the Dataverse>Dataflow section where I could edit them. However, after import I decided to do some changes of the dataflows in the source environment.
For this reason:
- I deleted in the target env all the imported dataflows together with the imported solution
- made the changes of the dataflows in the source env
- re-exported the revised solution from the source env, and finally
- imported again to the target env.
As a result, the dataflows DID NOT RE-APPEAR in the Dataverse>Dataflow section as expected. The dataflow were however present in the imported solution. Multiple "Publishing" of both solution and dataflows did not help either.
I guess after I deleted the dataflows, their GUID still remained present in the system and therefore when adding dataflows with the same GUID they were not added to the Dataverse>Dataflow section.
It took me some time to dig but finally I found a fix.
In the "Admin center":
- go to "Environments>YOUR ENV>Settings>Data management>Bulk deletion"
- click New
- choose "Dataflows" in the dropdown + "Active" in the "Use Saved View", click preview
In my case there were present the dafaflows from the solution, which I deleted.
NB: This deleted both the dataflows from the solution and GUID records from the system (I assume).
After I deleted the solution and re-imported again, and the dataflows were back in the Dataverse>Dataflow as expected.
Hope this information may help.
