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 August 31st. Request your voucher.

Reply
lewisbaybutt5DT
Regular Visitor

Load error - relationships

Is there any way to get around this error? I have to be able to have multiple session bookings with the same 'booking type' which includes a fee on that booking type table. Surely this is possible? Thanks in advance for anyones help! 🙂

 

lewisbaybutt5DT_0-1636290390158.png

 

6 REPLIES 6
lewisbaybutt5DT
Regular Visitor

lewisbaybutt5DT_0-1636292680246.png

 

lewisbaybutt5DT
Regular Visitor

So am I unable to have multiple 'Session Types' with the same 'Fee' and then multiple 'Session Bookings' that lookup to each of those types? I have a session types table where the type name, fee and duration get stored. Then session bookings get made and the type is selected on the booking (lookup). I need to be able to have 2 session types with the same fee but a different duration. Is this not possible?

You need to use the appropriate relationship for your data. If there are multiple session types for a single booking, then you cannot have a 1-to-1 relationship between tables. You'd need a many-to-one or a many-to-many relationship. Any time a relationship has a 1 side, the values on that side must be unique.

I will have a go at these things but that data logic doesn't make much sense to me. Surely I would only use a many to many relationship if I needed to relate multiple session types to multiple session bookings? I just want to relate a single session type to multiple session bookings. This works well in my dataverse model-driven power app, so is it just Power Bi that works like this and requires the different relationship. I want to be able to keep my single form column lookup on my session bookings form in my app, so can I just create the many to many relationship in Power Bi and then will it work?

Thanks in advance

If it's one-to-many, then use a one-to-many relationship, not a one-to-one. A one-to-one relationship requires unique values on both sides.

Fowmy
Super User
Super User

@lewisbaybutt5DT 

Before creating the relationship, make sure you have no duplicates in your column you use for the one side of the One-To-Many relationship

Did I answer your question? Mark my post as a solution! and hit thumbs up


Subscribe and learn Power BI from these videos

Website LinkedIn PBI User Group

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

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

July PBI25 Carousel

Power BI Monthly Update - July 2025

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