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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Provide warning indication when Gen2 dataflows run, but not all fields exist in the destination tabl

If you create a Gen2 dataflow and set the data destination to "DWH" you can create a table in the DWH.

If you later modify the dataflow to add a column, this column doesn't appear in the DWH.

When you publish the report or when you run the dataflow THERE IS NO INDICATION OF A PROBLEM - everything looks good.

 

Please provide some indication that there is an issue so that the developer can fix it.

Status: Need Clarification

Hi!

After adding a new column to your query, what message do you receive when you go through column mapping of your destination? You should be able to see a message through this dialog that tells you about the schema difference and how you can only map to the existing columns in your destination.

 

The information about the column maping is different from the query itself. The query itself contains the logic for the output, but the column mapping and the destination dialog is the one that contains the logic as to how your query should be loading data to the destination. More information about this process can be found in the article below:

Dataflow Gen2 data destinations and managed settings - Microsoft Fabric | Microsoft Learn  

Comments
miguel
Community Admin
Status changed to: Need Clarification

Hi!

After adding a new column to your query, what message do you receive when you go through column mapping of your destination? You should be able to see a message through this dialog that tells you about the schema difference and how you can only map to the existing columns in your destination.

 

The information about the column maping is different from the query itself. The query itself contains the logic for the output, but the column mapping and the destination dialog is the one that contains the logic as to how your query should be loading data to the destination. More information about this process can be found in the article below:

Dataflow Gen2 data destinations and managed settings - Microsoft Fabric | Microsoft Learn  

Steve-DataCoura
Advocate I
You're missing the point here. If the user has changed the schema in a way that breaks the column mapping, then the UI should indicate this so the user can spot and correct the problem. The user shouldn't have to open a different aspect of the UI, like destination table interface, to discover that there is a problem. Help 'em out.