Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi Chaps, I'm not sure if this has been answered, but I did some digging and couldn't find anything.
I have Gen2 Dataflow in Fabric, which picks a warehouse as the destination. I've created 3 schemas, and I like the data to be placed in the schema of my choice; however, this is not the behaviour as it places the files automatically in the dbo schema. I do not see any options for this, and manually moving the table to another schema is not ideal.
My 3 schemas:
- Bronze <-- this is where I like to drop the files from dataflows
- Silver
- Gold
Any ideas?
Hi
On Data destination:
Go to Advanced options and set full hierarchy True
Now you can see all shcemas
Regards,
Dario
Agreed. It would be very beneficial to configure a Dataflow Gen2 to have its Warehouse destination be a NEW table in something other than the dbo schema.
If you try to use two-part reference in the (new) Table Name option while configuring the destination, yoiu get an error that the name can contain only letters and numbers, etc.
Side note: two-part object reference is STANDARD OPERATING PROCEDURES and also considered a BEST PRACTICE. I ALWAYS reference tables with two-part names, even when they are in the dbo schema.
NOT having this is a huge pain!.
Proud to be a Super User! | |
Hello, I have the same problem, I want to chose a different schema for my dataflow destination, did you find a solution except the one that is manual?
Thank you
I have had the same issue. Unable to load the data into schemas other than dbo. I had to create a table under my own schema and then select the existing table in the destination option.
It would be great if we could select the 'new table' and select the destination warehouse and drill it down to select the required schema.
There is a shortcut I managed to figure out, and it does the job. If you create the table under the new schema, you can change the destination and select the existing table under the correct schema.
Ideally this option should be available under the wizard but I understand the app is still in beta mode.
Yes, this works, but if your table is of any decent size, manually creating it is a pain, so SSMS comes into play here as it allows the "Script table as >> Create..." option. Fabric does NOT have this capability, unfortunately.
Proud to be a Super User! | |
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!