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

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
garythomannCoGC
Impactful Individual
Impactful Individual

power bi desktop - append queries as new - missing column

Using the 'Append Queries as New' in the Power Query Editor to  combine several tables and some columns were missing.

Tried the process with just two of the tables and same story.  

A very simple concept as shown in the m$ document page  Append queries dated  16-2-2022.

Maybe there is a bug?

Video showing the process but just for the first two tables  Two table append 

 

Bug link  power bi desktop - append queries as new - missing column 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @garythomannCoGC ,

Are those missing columns custom columns or calculated columns? If they are calculated columns, then they are not visible in Power Query Editor. You can read the following blogs to understand the difference between calculated columns and custom columns. Unlike custom columns that are created as part of a query by using Add Custom Column in Power Query Editor, calculated columns that are created in Report view or Data view are based on data you've already loaded into the model.

Main differences between Calculate Column Vs Custom Column in Power BI

Custom Column

  • When you add a Custom Column in Power Query Editor, you have to use M language.
  • Creating a new Custom Column or even performing bit changes on the currently created Custom Column requires more time depends on the table size because it needs a full refresh of the table.
  • The size of the Custom Column in Power Query is always smaller than the created Calculated Column in DAX.
  • You can’t use DAX expressions in a Custom Column in Power Query Editor.

Calculated Column

  • When you add a Calculated Column in Data View or Report View, you have to use DAX.
  • Creating a new DAX Calculated Column is faster because it does not require a full refresh of the table.
  • The size of the DAX Calculated Column is always bigger than the created Custom Column in Power Query.
  • You can’t use M language in a Calculated Column in Report or Data View in Power BI.

Power BI: Custom Column Vs Calculated Column

In addtion, you can refer the following thread to get what you want.

Merge Query does not carry over new columns created

There is no way to see DAX columns in Power Query. The engine runs step by step, imagine the model is created with power query and DAX create things when the model is created.

 

The way to go is Adding a Custom Column in Power Query that will let you write code. That way if you have conditions, you can replicate them. We can help you if you show the DAX code (unless it is a crazy 20 lines business code hahaha)


Why Custom Columns are missing from Edit Query view?

Best Regards

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Hi @garythomannCoGC ,

Are those missing columns custom columns or calculated columns? If they are calculated columns, then they are not visible in Power Query Editor. You can read the following blogs to understand the difference between calculated columns and custom columns. Unlike custom columns that are created as part of a query by using Add Custom Column in Power Query Editor, calculated columns that are created in Report view or Data view are based on data you've already loaded into the model.

Main differences between Calculate Column Vs Custom Column in Power BI

Custom Column

  • When you add a Custom Column in Power Query Editor, you have to use M language.
  • Creating a new Custom Column or even performing bit changes on the currently created Custom Column requires more time depends on the table size because it needs a full refresh of the table.
  • The size of the Custom Column in Power Query is always smaller than the created Calculated Column in DAX.
  • You can’t use DAX expressions in a Custom Column in Power Query Editor.

Calculated Column

  • When you add a Calculated Column in Data View or Report View, you have to use DAX.
  • Creating a new DAX Calculated Column is faster because it does not require a full refresh of the table.
  • The size of the DAX Calculated Column is always bigger than the created Custom Column in Power Query.
  • You can’t use M language in a Calculated Column in Report or Data View in Power BI.

Power BI: Custom Column Vs Calculated Column

In addtion, you can refer the following thread to get what you want.

Merge Query does not carry over new columns created

There is no way to see DAX columns in Power Query. The engine runs step by step, imagine the model is created with power query and DAX create things when the model is created.

 

The way to go is Adding a Custom Column in Power Query that will let you write code. That way if you have conditions, you can replicate them. We can help you if you show the DAX code (unless it is a crazy 20 lines business code hahaha)


Why Custom Columns are missing from Edit Query view?

Best Regards

garythomannCoGC
Impactful Individual
Impactful Individual

Looks like the calculated columns do not get included in the append process.  Why?

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors