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.
Hi!
I did confirmed that Schemas are only available in Data Warehouses not data lakes and therefore the "Schema options on publish" is only available under the Warehouse experience. I created a Data Warehouse within the "Data Engineer" experience and went througt the exercise with the same results, so I guess this confirms that have nothing to do the experience. The "Use automatic settings" is not enabled under any of the tested scenarios. In summary the questions are:
1- How the "Use automatic settings" switch (on/off) gets enabled? (see "Choose destination settings" while defining a Dataflow).
2- In the advance settings I have the option to edit the source selection script, but not for the destination, therefore... how can I have access to the script that define the destination?
Thats it, once I am able to disable the automatic settings I will have full control of the "Schema options" and select the destination.
I hope that I can move up with this roadblock since its escential to be able to create schemas and put data in those as needed, everthing should not go to "dbo", actually "dbo" is at times a dumpster and people just add the groupings as a first word in the table name, making a lot harder to manage group security.
Can you help?