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

Grow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.

Reply
ROG
Responsive Resident
Responsive Resident

Not able to create to a relationship

Hey guys,

 

I need to connect two tables, but I'm getting the error below.

 

ROG_0-1702068797059.png

 

 

1 table comes from databricks

2nd table was created in PBI with a union statement (see below)

 
Table - TopCarrier =
UNION(
    VALUES(feRR_ads_1143_weekly_porting_5c[Carrier]),
ROW("Carrier","Others")
)

 

 

How can I connect them?

 

Many thanks.

 

1 ACCEPTED SOLUTION
v-junyant-msft
Community Support
Community Support

Hi @ROG ,

The error message “A circular dependency was detected” usually occurs when there is a loop in the relationship between two tables. This means that one table depends on another table, which in turn depends on the first table. This creates a cycle that Power BI cannot resolve.
Please check the relationships between the tables and make sure that there are no loops and check the calculated columns or calculated tables and make sure that they do not reference each other in a circular manner.
If you find a circular dependency, you will need to restructure your relationships. This might involve removing or changing the direction of some relationships. Ensure that your relationships flow in one direction to prevent loops.
If you are unable to solve your problem, could you please provide your sample data and data model?

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

3 REPLIES 3
v-junyant-msft
Community Support
Community Support

Hi @ROG ,

The error message “A circular dependency was detected” usually occurs when there is a loop in the relationship between two tables. This means that one table depends on another table, which in turn depends on the first table. This creates a cycle that Power BI cannot resolve.
Please check the relationships between the tables and make sure that there are no loops and check the calculated columns or calculated tables and make sure that they do not reference each other in a circular manner.
If you find a circular dependency, you will need to restructure your relationships. This might involve removing or changing the direction of some relationships. Ensure that your relationships flow in one direction to prevent loops.
If you are unable to solve your problem, could you please provide your sample data and data model?

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

VahidDM
Super User
Super User

Hey @ROG 

If you create the second Table in Power Query then this will be fixed.

 

If this post helps, please consider accepting it as the solution to help the other members find it more quickly.

Appreciate your Kudos!! 

Badges.jpg

LinkedIn | Twitter | Blog | YouTube 

ROG
Responsive Resident
Responsive Resident

Thanks @VahidDM 

 

I have tried using the same logic above in PQ, but no success.

Would you be able to advice?

Helpful resources

Announcements
RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.

MayPowerBICarousel1

Power BI Monthly Update - May 2024

Check out the May 2024 Power BI update to learn about new features.