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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.

Reply
Anonymous
Not applicable

Not being able to merge two tables in Power Query

Hey All,

 

I am new to Power BI and struggling with merging queries.

Could someone please tell me why I am getting warning sign against so many tables while I am trying to merge "Dim_Date" with some other table using "Merge Queries". I am trying to merge "Dim_Date" with "Dates_Cross_Join" but not being able to do so due to the warning sign and "No Preview is available". Image attached for reference.

But when I try with "Merge queries as New", it works fine. 

 

Image.png

Your help would be greatly appreciated.

 

Thanks in advance!

2 ACCEPTED SOLUTIONS
Greg_Deckler
Community Champion
Community Champion

@Anonymous Perhaps there is some sort of dependency between those two queries? Does one refer to the other?



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

View solution in original post

@Anonymous I would say 100% that is the issue and why it works if you merge new, because with merge new it will load the queries in the right order , load Dim_Date and then Shipment and then Dates_Cross_Join and then the new merge query. Otherwise, you have effectively created a circular reference and it is not going to like that.


Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

View solution in original post

4 REPLIES 4
leyes
Frequent Visitor

As others commented below, maybe there's a dependency between those two queries. You can turn this around using DAX OR...

You can right click on Dim_Date and press "Reference". It will create another query called "Dim_Date (2)" and you com merge it with "Dates_Cross_Join". Doing this, you have to start working on "Dim_Date (2)" besides "Dim_Date".

 

The difference between 'duplicate' and 'reference': Solved: Difference between Reference and Duplicate - Microsoft Power BI Community

Greg_Deckler
Community Champion
Community Champion

@Anonymous Perhaps there is some sort of dependency between those two queries? Does one refer to the other?



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...
Anonymous
Not applicable

@Greg_Deckler Hey.. "Dates_Cross_Join" is a reference of "Shipment" table and "Shipment" table is a merge of "Dim_Date" and another table.

Could this be a reason behind the problem?

@Anonymous I would say 100% that is the issue and why it works if you merge new, because with merge new it will load the queries in the right order , load Dim_Date and then Shipment and then Dates_Cross_Join and then the new merge query. Otherwise, you have effectively created a circular reference and it is not going to like that.


Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors