Forum Discussion
Post PatronWhy the 2 additional rows added to Dataflow Gen 2?
Could someone explains why those 2 additional rows keep adding to my dataflow? Previously without those 2 additional rows the Dataflow works fine, and I remove those 2 additional rows, they are OK too, but somehow at times, those 2 rows are added not by me, but by Fabric itself.
Hi tan_thiamhuat,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also thanks for lbendlin, for his inputs on this thread.The two additional steps you are encountering are automatically added by Microsoft Fabric during schema validation. This typically occurs when the system identifies that your source (Dim_Channel) is not a structured table or contains unsupported types such as records, lists, or functions.
To address this and prevent Fabric from reintroducing those rows, you can simplify and explicitly define the output schema. Below is a refined version of your query that avoids the automatic system-generated steps:
M query:let // Load source data directly as a structured table Source = Sql.Database("your_server", "your_database"), Dim_Channel = Source{[Schema = "dbo", Item = "Dim_Channel"]}[Data], // Select only the required columns to enforce a fixed schema CleanedData = Table.SelectColumns(Dim_Channel, {"ChannelID", "ChannelName", "IsActive"}) // <-- Adjust columns as needed in CleanedData
If you are uncertain about which columns to select, please let me know, and we can customize this together.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
2 Replies
- lbendlin
Super User
The data produced by Power Query's last step has to be in table format and can only contain simple column types like text, numbers, or times. Any complex column types like tables, records, lists, binary are not permitted.
v-kpoloju-msftCommunity Support
Hi tan_thiamhuat,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also thanks for lbendlin, for his inputs on this thread.The two additional steps you are encountering are automatically added by Microsoft Fabric during schema validation. This typically occurs when the system identifies that your source (Dim_Channel) is not a structured table or contains unsupported types such as records, lists, or functions.
To address this and prevent Fabric from reintroducing those rows, you can simplify and explicitly define the output schema. Below is a refined version of your query that avoids the automatic system-generated steps:
M query:let // Load source data directly as a structured table Source = Sql.Database("your_server", "your_database"), Dim_Channel = Source{[Schema = "dbo", Item = "Dim_Channel"]}[Data], // Select only the required columns to enforce a fixed schema CleanedData = Table.SelectColumns(Dim_Channel, {"ChannelID", "ChannelName", "IsActive"}) // <-- Adjust columns as needed in CleanedData
If you are uncertain about which columns to select, please let me know, and we can customize this together.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
