Entity Relationship in Model driven app

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

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.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Verified answer

v-siky-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No