Dataflow (Gen2): Specifying target table schema if is a new table

[dhorrall]

I tried to create a new table in a target Warehouse.

When I tried to create a new table with tst.theTable, 

I ended up with:

It seems to use the schema from the 'source' table I was extracting from (which was 'coupa')

I see no place to specifiy the target schema explicitly other than what I tried with 'dot' notation in the table name field.

Putting aside the fact that I am writing to a Fabric Warehouse, even though I chose Azure SQL Server as the target.  This seems like a bug.

[danjo914]

A crude workaround involves initially creating the table within the desired schema, then selecting it as an existing table in your dataflow. Afterwards, you can utilize the dataflow to generate the table under the dbo schema, perform a drop and create action to move it to the new schema, and redirect the dataflow. Note that default data types like bigints and varchar (8000) will be applied initially, but they can be corrected using the drop & create query.

[webchris]

Okay great, this will definately help. Many thanks for the idea!

[Pfisterbi]

Run into the same issue.

We need a possibility to choose a schema.

[webchris]

Yeah, I think so, too...

[SidJay]

There isn't currently a way to customize the schema. We are tracking this as a feature gap.

[webchris]

What is the status of this, is there a chance to track this?

[miquelladeboer · Accepted solution]

This is still on our feature list, but we do not have a current timeline yet. Any improvements to outputdestinations and their timelines can be tracked here: What's new and planned for Data Factory in Microsoft Fabric - Microsoft Fabric | Microsoft Learn

[miguel]

Thank you for the feedback! I went ahead and forwarded this information to the appropriate internal team so they can take a look at this thread.

[webchris]

Hi Miguel @miguel 

Any news on this?