Forum Discussion
Memorable MemberBUG::New table in data warehouse not detected
Memorable MemberEDIT::one needs to set a destination and then only disable staging, in order for the the Publish button to not disappear. There is no way to publish if staging is disabled and no destination is set.
Interesting... the Publish button does not disappear if I set the destination before disabling Enable staging. So I tried again but this time the destination is a lakehouse I created just for this. And it does not work. No data, no table created by the DF in the lakehouse. This is with one DF, not the workaround with 2 DFs. Whereas with Enable staging, at least you get the data but not the source column names, which get replaced by generic names such as Column1, Column2, etc....
My network admin did open port 1433 and set the Firewall rule according to the Microwsoft doc for the on-prem Power BI data gateway, so...
Here is the screenshot:
Microsoft EmployeeFrom our telemetry it does seem like a gateway connectivity issue. Can you check the error message that's shown when you click on the Sector_TS_* activity from the refresh history dialog?
We do have a blog post that describes limitations and considerations when using Data Gateway with output destination in the context of Dataflow Gen2: On-premises data gateway considerations for data destinations in Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
Finally, it is by design to disallow publishing a dataflow that only contains queries that are not marked as staged nor have an output destination set.
Thanks,
Frank.
Hello Element115 ,
We haven’t heard from you after the last response by frlunett - and was just checking back to see if you have a resolution yet .
In case if you have any resolution please do share that same with the community as it can be helpful to others .
Otherwise, will respond back with the more details and we will try to help .Hi Element115 ,
We haven’t heard from you after the last response by @frlunett - and was just checking back to see if you have a resolution yet .
In case if you have any resolution please do share that same with the community as it can be helpful to others .
Otherwise, will respond back with the more details and we will try to help .- Element115
Apologies, I got sidetracked by all the support tickets opened for the other bugs that popped up when using a lakehouse to ingest data from the on-prem DB. Let's put the data warehouse on hold for now, as our scenario benefits more from a lakehouse anyway and let's see if support manages to find a solution to the issues blocking not only ingestion from on-prem, but also from a lakehouse source.
Here is to hoping that the new OPGW will solve all these issues and allow bulk data copy from an on-prem DB to a lakehouse using a simple pipeline.
- Element115
Thanks Frank, sorry for the late reply as I got distracted by all the other support tickets opened. The data gateway works fine, well at least with the Power BI Service, the right ports are opened in the firewall and so on. Let's pause the data warehouse issue for now as all the issues concerning data ingestion in the lakehouse are being worked on.