The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
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
Solved! Go to Solution.
Hi @mike9999
Thanks,
Jai Rathinavel
Proud to be a Super User! | |
Hi @mike9999
Thanks,
Jai Rathinavel
Proud to be a 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”.