Forum Discussion
DataFlow Choose destination settings "Use automatic settings" disabled
Please check the documentation available for this:
answering some of the questions that I've seen on this thread:
- Automatic settings are only supported for Lakehouse and Azure SQL database
- Automatic settings can only be applied to new tables
- Dynamic table schema options on publish can only be selected when using the "Replace" update method
As mentioned in some previous replies, there are some experiences that perhaps don't exist today in Dataflow Gen2. For any of those please feel free to post an idea in the Fabric ideas portal (aka.ms/FabricIdeas)
if you can't use the "automatic settings" when trying to create a new table to a Lakehouse or an Azure SQL DB, please feel free to open a support ticket and reply to this message with the case number. I'll elevate it and have the engineering team take a closer look as to what might be causing such bug.
Please do refer to the documentation available that covers the current supported scenarios and limitations.
Frithjof,
Got your follow-up email. If the "Dynamic Schema" is related to the table definition and not to database "Schemas" then what I am reporting is an issue since there should be a way to copy the data into a destination schema different from "dbo".
As possible, can you help scalating this issue or let me know were is the best place to follow-up with this issue?
I tested it, and it seems it is actually possible in Dataflows Gen2 to write to another database schema instead of "dbo".
Here's what I did:
1. Create a new schema in my Data Warehouse.
2. Create a table in the new schema, inside the Data Warehouse experience.
3. In the Dataflows Gen2, in the destination settings choose "Existing table" and then I could find my schema and table.