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
