Forum Discussion
Create Dataflow Gen 2 without Data destination to test - unable to add Data destination later
Hey!
The data destination logic is set up as an extra (last) step to a query of your choosing. Make sure that you select the query of your choice and then you should be able to see the "output destination" button in the ribbon, the diagram view or even in the applied steps section available to you.
If you are not able to see it, could you please share a screenshot of what you see? Just make sure that you select a query first.
Hi,
where is the solution please ? I have always the same issue. When I prepare a dataflow gen2 (reading from sharepoint, load to lakehouse), everything looks great.... but then when I publish it Fabric generates a new tasks to Flow with a alert/bug.
If a delete these task. I can not to add destination (lakehouse) again anymore.
task with alert:
let
WriteToDatabaseTableFrom_TransformForOutputToDatabaseTableFrom_Query = Pipeline.ExecuteAction(ValueAction.WithTransaction([Target = #"DestinationForWriteToDatabaseTableFrom_Query (2)"], (txn) => {TableAction.DeleteRows(txn[Target]), TableAction.InsertRows(txn[Target], TransformForOutputToDatabaseTableFrom_Query), Action.DoNothing}))
in
WriteToDatabaseTableFrom_TransformForOutputToDatabaseTableFrom_Query
with error message:
Expression.Error: The import Pipeline.ExecuteAction matches no exports. Did you miss a module reference?
I am not even google this function.
Hi,
Did you create this dataflow from a template that you had where the load destination was defined?
Thanks for quick response.
First time I created it from the ground.
Than I left only first part of flow (parameters and query) I created a template.
Always ended up with the same result.
we have a known bug where the template gets exported with mashup definition (effectively queries) that shouldn't be surfaced to the end-user such as:
WriteToDatabaseTableFrom_TransformForOutputToDatabaseTableFrom_Query
Our recommendation is to remove this and any other queries related to the output destination (Write, and Transform queries). We will be posting an article later this week with more information, but at the moment my believe is that you're reaching that error because of it.
If you'd like further assistance with your particular scenario, which is a bit different than the one described in this thread, please go ahead and create a new thead where we can engage.