I do not see existing table in dataflow gen2 destination warehouse

[DavidPi]

I created table in Warehouse.

Then I created dataflow gen2 and tryed to set destination to this existing table. 

But I do not see any tables under my warehouse.

Where do I make the miskate?

[romankorchak]

Having the same issue - I created a dataflow gen 2 with Datalake destination (creating new table), which worked fine.
Then I wanted to have data added to the table on each refresh so I went to change destionation to "Existing Table", but itsnot finding the table that was created on initial refresh (which was done with "New table" option).
If this issue was resolved - may I know how
Thanks

[DavidPi]

Unfortunately, not yet. Advice is to set rule describes here - On-premises data gateway considerations for data destinations in Dataflow Gen2 - Microsoft Fabric | ...

I dont believe this will help. We are waiting for our security department decision (they dont want to allow general url address).

[mllopis]

Oh, my bad - I think I got this the other way around and you started by creating the table in DW directly, not via the Dataflows Output Destination UI.

Sometimes there can be a lag between creation of tables in the DW Editor experience and the table being visible in other clients - Did the issue persist after a few minutes and refreshing/re-entering the Output Destinations UI in Dataflows? Were you able to query this table using other SQL clients?

Thanks,
M.

[DavidPi]

Unfortunately, the situation is the same today. I see table in DatawarehouseTest1, I can select from this empty table. But I don't see it in Dataflow under Warehouse destination.

Warehouse and Dataflow are in the same workspace. I am admin of this workspace.

[miguel]

Please go ahead and create a support ticket so an engineer can take a closer look at this case.

https://support.fabric.microsoft.com/support

[DavidPi]

I have created a support ticket. I will know the result. Thank you.

[Anonymous · Accepted solution]

Hi @DavidPi ,
Thanks for creating a Support Ticket. 
It would be a great help if you can provide the details of the Support Ticket so we can track it for further information. 
Thank you

[DavidPi]

TrackingID#2310030050000199

[CristinaCT]

Hi! Can I ask what was the resolution of this issue? I am facing the exact same problem.

Thanks!

[DavidPi]

The solution is not yet available. Microsoft claims that the reason is improperly configured FW rules on gateways/proxy. At the same time, we are unable to load on-premises data (Oracle) into the lakehouse. However, I really don't know if that's the actual reason, and it seems a bit architecturally peculiar to me.

[mllopis]

Hi DavidPi,

Creation of a new table in an output destination will happen only as part of dataflow refresh/execution - To confirm, after configuring your output destination, were you able to Publish your dataflow (and have it complete a successful Refresh operation - note that the initial refresh of a dataflow will be kicked off automatically upon succesfully publishing it)?

You can check in the Refresh History (via "..." menu for your dataflow in the workspace view) to understand whether the refresh happened and its success/failure status.

Hope that helps