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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Use Key Field for Rela...
Power Apps
Unanswered

Use Key Field for Relationship

(0) ShareShare
ReportReport
Posted on by 75

Dear All,

I created a table called C_Student. It automatically created a field named crxxx_c_studentid, and this is unique and required. I changed the primary column name to StudName. I also created FirstName,  LastName , and StudID columns. To create a key, I was presented with a few columns: FirstName, Import Sequnce Number, LastName, Record Created On, StudID,  StudName, Time Zone Rule Version Number, UTC Conversion Time Zone.  

 

StudID is an Autonumber. I would like to use StudID as my Key. However, if you tried to create a relationship, say between C_Student table as your Parent table to a child table like C_Class, I would like the relationship to be StudID in C_Student to relate to StudID in C_Class, but it is picking C_Student as the Lookup column name. In other words, it looked like C_Student column is automatically created to relate the child table (C_Class). If this is the case, of what importance is adding Key to a table in Dataverse? 

 

My thinking now is that the only way I can do that is not to establish the relationship between the tables as provided on the tab to "Add Relationship," but to create each table, then, create a key and select the column that I want  in the Parent table, and then,  create the child table and add a column with the same name as the selected key column in the child table, then, set it as Lookup to the Parent table. Please advise on a better approach. Meanwhile, I noticed that Autonumber is not Unique. Is there a way to make it Unique? 

Your advice to this request is greatly appreciated.

 

Sincerely,

Isaiah A.

 

 

I have the same question (0)
  • codevenkat Profile Picture
    126 on at

    Hi @IsaiahA ,

    You are going in the right approach only, create parent table first and then child table. Then go to the parent table and establish 1 to many relation ship with child table. And go to child table form keep the look up of parent table from list of available columns.

    For autonumber, hope you have followed the same approach https://docs.microsoft.com/en-us/powerapps/maker/data-platform/autonumber-fields , make sure you give some uniqueness to the name.

     

    If this post helps you with your problem, please mark your as Accepted solution.If you like my response, please give it a Thumbs Up.

    My Blog : https://venkatasubbaraopolisetty.com/

     

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 739 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 343 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard