web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Understanding Table Re...
Power Apps
Unanswered

Understanding Table Relationships

(0) ShareShare
ReportReport
Posted on by 49

I have two existing tables and I want to build a view. From what I understand, I have to build a relationship between the two tables  before I can create a view that uses both tables. When I create a relationship, the interface does not ask me which fields I want to be part of the relationship. This does not make sense to me. I am an old SQL guy and this does not make sense.

I have the same question (0)
  • a33ik Profile Picture
    3,306 Most Valuable Professional on at

    What kind of relationship are you trying to add? Is it safe to assume it's N-N? In this case, fields would be assigned by PK fields of both entities.

  • Lukewarm Profile Picture
    49 on at

    one to many.

  • a33ik Profile Picture
    3,306 Most Valuable Professional on at

    When you create a relationship UI asks you to provide a related table and the column in the related table.

    You can check the following post - https://www.linkedin.com/pulse/relationships-types-behaviors-dataverse-kumar-manish-csm-pmp-/

  • Fubar Profile Picture
    8,487 Super User 2026 Season 1 on at

    Unlike SQL, Dataverse manages the PK and FK.

    The PK is a system generated GUID that is held in a column with the same logical schema name as the Table but with a suffix of "id" e.g. for a table with schema "new_mytable" the PK will be in "new_mytableid"   (You can extend this by creating Alternate Keys)

     

    The FK is a little bit more difficult conceptually - the FK is always a GUID and the only way you can create a field of that type GUID is to create a field of type Lookup (and doing so will automatically create a FK).

    • If you create a Lookup Field - this is automatically creating a Relationship and creating an FK (the table with the Lookup field is the Child table)
    • If you manually create a Relationship you will be prompted for the 2 tables, and for the child table it will prefill values for the Lookup (but you can change them if you desire) and it will create the Lookup on the Child. 
    • As the FK is always a Lookup field (and a Lookup field is already an FK) you cannot select an existing field.

    Fubar_0-1700542761658.png

     

    Also, whilst the FK linkage is the the GUID, the Lookup on the Child will display the Primary Name Column value from the parent.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 505

#2
WarrenBelz Profile Picture

WarrenBelz 502 Most Valuable Professional

#3
Haque Profile Picture

Haque 324

Last 30 days Overall leaderboard