Dataflow Gen 2 fails validation on new lakehouse only

[alloowishus]

I just created my first Dataflow Gen 2 activity, I setup my merges and joins. I created a new lakehouse for this destination in my workspace. When I go to select it as a destination, i can see the new lakehouse and select it from my connection. However when I finish the mapping and click "save settings" on the new table, I get an error. 

"lakehouse .... does not exist or you do not have the necessary permissions. ErrorCode: EntityNotFound"

It works with existing lakehouses just not this one. All on my own workspace.

[v-tejrama]

Hi @alloowishus ,

Thank you @arabalca for the response provided!

Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

Thank you.

[v-tejrama]

Hi @alloowishus ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[arabalca]

Hi @alloowishus 

I've been looking into your case and I think the issue is that the new Lakehouse hasn't fully finished provisioning before the Dataflow tries to validate it against the Fabric backend — hence the EntityNotFound error, even though it already shows up in the UI.

Also, since you created the Lakehouse yourself and you're an Admin in the workspace, permissions shouldn't be the problem here — so we can rule that out.

A few things you can try:

• Before setting the Lakehouse as a destination in the Dataflow, create the target table manually in the Lakehouse first. This helps Fabric fully register the object before the Dataflow tries to reference it.

• Publish the Dataflow first without configuring the destination, then edit it afterwards to add the new Lakehouse as the destination. This is usually the most effective workaround.

• Check in OneLake Explorer that the Lakehouse already has the Tables/ folder visible, which confirms that provisioning has completed.

• If it still fails, delete the Lakehouse, recreate it, wait a couple of minutes, and try again.

Hope this helps! Let us know how it goes.

If this helped solve your problem, I would appreciate it if you could mark the response as the accepted solution and give it a "Like" 👍

[MJParikh · Accepted solution]

Hi @alloowishus,

When you create a new lakehouse in Fabric, the metadata registration across the service takes a few minutes to fully settle. Dataflow Gen 2 tries to resolve the destination before that process completes and throws EntityNotFound as a result.

Try these steps in order:

1. Wait 3 to 5 minutes after creating the lakehouse before configuring it as a destination in Dataflow Gen 2.
2. Refresh your browser completely, then reopen the dataflow and reselect Lakehouse as the destination.
3. If the error persists, navigate to your workspace, open the lakehouse directly, and confirm it loads without errors. This forces a metadata sync on your session.

Please re-enter the Dataflow Gen 2 destination mapping and save the settings once more.

The fact that existing lakehouses work confirms your permissions are fine. The new lakehouse simply was not fully registered when you attempted to save the destination mapping.

If you still see the error after waiting and refreshing, try creating the lakehouse from the workspace home page rather than from within the dataflow configuration screen. That approach gives the registration process more time before you reference it in a pipeline. Hope this helps!

Thank you!
Proud to be a Super User!
📩 Need more help?
✔️ Don’t forget to Accept as Solution if this guidance worked for you.
💛 Your Like motivates me to keep helpingThank you!