Copy Data Destination Configuration (Dynamic Lakehouse Content)

Initially, the "Copy Data" activity allowed choosing lakehouses as destinations and worked seamlessly even with dynamic content for lakehouse selection. An update introduced an option to choose either a lakehouse or a connection to supported destinations. We opted for the connection option to maintain dynamicity. Fabric requires a schema name and table name for this option, but the data was not copied to the proper destination table.

We are using table_name as dynamic content inside the pipeline