Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

Reply
mike9999
Helper I
Helper I

Dataflow gen2 binding to default data destination

Hey-

Whenever I configure the "Bind to default data destination" for the output of a dataflow gen2 to the Lakehouse - it attempts to bind internal dataflow functions like "Transform Sample file", "Transform Sample file(2)", etc. Dataflows creates these as placeholders automatically when combining multiple binary files. They are not intended to be kept as bindings/outputs. Is there an easy way to automatically skip these and prevent them from being accidently written to the lakehouses?

 

I have a lot of output files so it is tedious to disable all the transform sample files regularly. 

 

Mike

1 ACCEPTED SOLUTION
Jai-Rathinavel
Super User
Super User

Hi @mike9999 

  • Currently there are no settings in place to disable Functions or Sample files getting written to the lakehouse / warehouse.
  • But it is not necessary to have a Transform file / funtions in the Power Query layer. If you see the Transform file funtions those are all created by Power Query automatically. You can copy the logic of the Transform File function and past it inside your main query logic.
  • Once you have copied the logic and fixed your M code. You can delete the transformation functions and sample file associated with it.

Thanks,

Jai Rathinavel




Did I answer your question? Mark my post as a solution!

Proud to be a Super User!





View solution in original post

2 REPLIES 2
Jai-Rathinavel
Super User
Super User

Hi @mike9999 

  • Currently there are no settings in place to disable Functions or Sample files getting written to the lakehouse / warehouse.
  • But it is not necessary to have a Transform file / funtions in the Power Query layer. If you see the Transform file funtions those are all created by Power Query automatically. You can copy the logic of the Transform File function and past it inside your main query logic.
  • Once you have copied the logic and fixed your M code. You can delete the transformation functions and sample file associated with it.

Thanks,

Jai Rathinavel




Did I answer your question? Mark my post as a solution!

Proud to be a Super User!





rohit1991
Super User
Super User

Hi @mike9999 ,

This is a common pain point when working with Dataflow Gen2 in Power BI, especially if you’re combining multiple files. “Transform Sample file” queries get created automatically, and binding all outputs to the default data destination tries to include them too.

 

Unfortunately, there’s currently no automatic built-in setting to skip these system-generated queries when binding outputs. You still have to manually uncheck or disable them from being written to the lakehouse.

 

Workarounds:

  • Naming Convention: As a best practice, always name your “real” output tables with a clear, consistent prefix (e.g., “tbl_” or “df_”). This makes it easier to batch-select only what you want in the list.

  • Manual Filtering: When binding, sort or filter by name and deselect any queries that start with “Transform Sample file”.


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.