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

Community site session details

Session Id : A7PFGpxjqX+DwTCX3hpc+E
Power Apps - Microsoft Dataverse
Answered

Entity Relationship in Model driven app

Like (0) ShareShare
ReportReport
Posted on 28 Apr 2020 04:22:00 by

 Hi All,

 

I have the below requirement:

EntityA  (columns --> entitya_id, name1)

EntityB  (columns --> entityb_id, name2)

 

EntityC

many to one relation to EntityA and also many to one relation to EntityB

columns --> entityc_id          entitya_id          entityb_id     name3

 

EntityD -- many to one relation to EntityC

columns are --> entityd_id      entityc_id      name4

 

1) View should look like:

name1       name2       name3       name4

 

2) Main Form should like

name1   Textbox

name2   Textbox

name3   Textbox

name4   Textbox

        save button

 

My main problems are:

Active view allows to show related fields, but when the data added - data shows some guid instead of actual data?

Main form allows to add the related entity's one field only as foreign key?

 

Please suggest how can i implement this scenario. Thank you.

I have the same question (0)
  • Community Power Platform Member Profile Picture
    on 30 Apr 2020 at 05:26:58
    Re: Entity Relationship in Model driven app

    Hi Sik,

     

    Your approach worked. Thank you. 

    I have created new fields in EntityD as Look up to EntityA and EntityB like N:1. It started showing the output in quick view form. 

  • Verified answer
    v-siky-msft Profile Picture
    on 28 Apr 2020 at 08:12:22
    Re: Entity Relationship in Model driven app

    Hi @Anonymous ,

     

    As far as I know, if you don't consider JavaScript development, It is only supported to show the parent fields on the child record by Quick View Forms or Calculated Fields.

     

    If you want the GrandParent fields(EntityA/EntityB) showing on the GrandChild record(EntityD), I think you might need to establish a 1:n linking EntityA/EntityB to EntityD (which could be copied via mapped fields or workflow from EntityC when you create EntityD) then you can surface EntityA/EntityB fields via Quick View Forms or Calculated Fields on the form.

     

    Note: the parent fields and grandparent fields are all read-only on Child/GrandChild record.

     

    Reference: Presenting Parent Information on a Child Record 

     

    Hope this helps.

    Sik

     

     

  • EricRegnier Profile Picture
    8,714 Most Valuable Professional on 28 Apr 2020 at 07:26:32
    Re: Entity Relationship in Model driven app

    Hi @Anonymous, please refer to my other response to your other post. The guid is the foreign key and what's saved in the database, what's shown on the view and forms is the primary field of the entity. This is detailed in one of the links in my other response (https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-create-entity). Suggest to have a read through them, it would give you the basics.

    Good luck

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Telen Wang – Community Spotlight

We are honored to recognize Telen Wang as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 637 Most Valuable Professional

#2
stampcoin Profile Picture

stampcoin 570 Super User 2025 Season 2

#3
Power Apps 1919 Profile Picture

Power Apps 1919 473

Featured topics