When setting a Default Destination inside Gen2 Dataflows, it would be nice to have schema support rather than everything going to dbo.
11 Comments
- Status changed:NewtoAbandoned
This is actually available today. You can read more about how to set up a default destination for a specific schema from the documentation below:
Dataflow Gen2 data destinations and managed settings - Microsoft Fabric | Microsoft Learn
Do feel free to post any new ideas if you have any suggestions to improve the existing functionality
- Um. Not sure if I'm missing something (or a bunch of somethings) but, I cannot do this for Lakehouses. It looks like I can get the Advanced option to appear for Warehouse: "In order to be able to write to schemas in these destinations you need to enable the Navigate using full hierarchy option under advanced options when you set up your connection." But, I want this for a Lakehouse. Am I missing something? Or is there, in fact, no way to do this?
- Sorry, not sure I understand what you mean. If I'm in a Dataflow and go to the Home menu, select Default Data Destination, then Add a dialog box pops up. I select OneLake Catalog, the LH I want, I get a Bind window of queries/tables to bind and then both dialog boxes close. The only way I was able to see the WH advanced option was by creating a new WH. I do not have a WH in this Workspace. Please tell me exactly what you'd like a screenshot of and how to get there and I'd be happy to help. Thanks
- Sorry, not sure I understand what you mean. If I'm in a Dataflow and go to the Home menu, select Default Data Destination, then Add a dialog box pops up. I select OneLake Catalog, the LH I want, I get a Bind window of queries/tables to bind and then both dialog boxes close. The only way I was able to see the WH advanced option was by creating a new WH. I do not have a WH in this Workspace. Please tell me exactly what you'd like a screenshot of and how to get there and I'd be happy to help. Thanks
The selection from OneLake catalog bypasses the navigational hierarchy, so it goes straight into the default mode.
For the advanced scenarios where you require schema support, you need to head over to the "New" module from the left and select the option for "Lakehouse"
once you've selected that, you will be able to choose the hierarchical path:
Hope this helps!
- Thanks. I didn't find that to be intuitive. To me, 'New with a Plus sign' means creating a new Lakehouse (or other Datastore). That does get me further, including allowing me to select the 'Full Nav' option Perhaps I'm still doing something wrong because the next screen allows me to select Lakehouses from several Workspaces but still does not allow me to select schemas. In other words, *** I see no difference if I select True or False. *** If I can help, please let me know. Thanks PS: My original issue was actually with the Copy Job not wanting to let me change the default destination schema en masse. I only stumbled across this because I was wondering if Dataflows might be a better option but it looks like they're not great for importing hundreds of tables. What I really want is Copy Job to be able let me pick 1 schema for all the hundreds of tables I'm bringing in instead of making me choose the schema for each table.
do feel free to post your questions about the feature in the forum using the link below:
Dataflow - Microsoft Fabric Community
I'll also make sure to pass your feedback to the team about how its not so intuitive how the "New" module means creating a New connection
- Maybe there is something I'm doing wrong, but, it makes no difference if I select True or False on the "Advanced" Menu, I don't see schemas to choose from.
- LKData would you, by any chance, try to write to a Lakehouse that doesn't have schemas enabled ? This option is relatively "new" as it was disabled initially while in preview. If this is not a schema enabled Lakehouse which is now the default, then that's expected. Can you verify that and eventually try with a new Lakehouse ?
