Hi Community,
Im planning to create a master detail in powerapps. But im confuse with the table structure.
Is my table structure is correct? Thanks
Table Name - Project
Column1 - ProjectID (AutoGenerated) (Number)
Column2 - ProjectName (String)
Table Name - Employees
Column1 - EmployeesID (AutoGenerated) (Number)
Column2 - ProjectID (Number)
Column3 - EmployeesName (String)
Relationship Key: Department->ProjectID - One to Many - Employees->ProjectID
Solved! Go to Solution.
One-to-many relationships is a Lookup field i.e. you create a Lookup field on the child record where the Lookup field is of type <Parent entity>.
Internally this relationship is via the internal GUID (system generated) of the parent record, but for display purposes shows the value of the "name" field of the parent record.
E.g in your example the minimum you would create of a one-to-many would be
Project
Employee
(and any other fields you want on the respective entities)
One-to-many relationships is a Lookup field i.e. you create a Lookup field on the child record where the Lookup field is of type <Parent entity>.
Internally this relationship is via the internal GUID (system generated) of the parent record, but for display purposes shows the value of the "name" field of the parent record.
E.g in your example the minimum you would create of a one-to-many would be
Project
Employee
(and any other fields you want on the respective entities)
Hi @Fubar
Thanks for the clarification.
I thought i need to created an reference id in the employee table.
Keep up the good job. 👍
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
15 | |
11 | |
8 | |
5 | |
4 |
User | Count |
---|---|
23 | |
16 | |
13 | |
12 | |
11 |