Answered

Is it possible to have data from parent and child entities on the same edit form?

(0) Share

Report

Posted on by Suresh_Satti

Hello All,

I have spent the last couple of days trying to figure out a way to build an edit form on an embedded canvas app (On Dynamics 365 Project) with the ability to edit fields on two entities i.e. the entity on which canvas app is embedded has N:1 relationship with the other entity. The form should have interlaced fields from the both the entities. Is this possible at all?

Thanks

Suresh

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Mira Ghaly 11,413 Moderator on at

Like (1)

Report

@sureshsatti

Any particular reason you are trying to do this using canvas app and not model driven app?

I would suggest here a Model Driven app where the main form will be on the parent entity and then a sub grid (Editable) for child records this is the easiest way you can edit parent and child from same form.

Was this reply helpful? Yes No
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (1)

Report

Hi @sureshsatti,

Yes it possible in all the scenarios: 1) edit the parent child entities within the embedded canvas app 2) edit parent entity from parent model-driven form and child within the embedded canvas app and 3) vice-versa. In your canvas app you just need to reference the 2 entities in the datasource and configure your app accordingly. To pass parameters from the model-driven form to the canvas app use the ModelDrivenFormIntegration object.

You can also perform this out-of-the-box with model-driven forms using FormComponentControl. It may simplify your overall solution. More info: https://docs.microsoft.com/powerapps/maker/model-driven-apps/form-component-control
Hope this helps!

Was this reply helpful? Yes No
Suresh_Satti 14 on at

Like (0)

Report

Thanks Mira, the purpose was to give the end user the experience of editing multi-entity data on a single form and the entity fields would need to be interlaced (for customers convenience) and needs to be visually formatted based on the customers needs. This is not possible on a model driven form and sub grids wouldn't be visually helpful for the end user.

Was this reply helpful? Yes No
Suresh_Satti 14 on at

Like (1)

Report

Thanks Eric, I am using the thrid option in your list. Now my doubt is, what would be a preferred approach out the of the two mentioned below. These are based on my research in last couple of weeks, there is a high chance that these way not even be correct and there could be even better and more streamlined approach.

1) Using an edit form and tweak the fields to point to the parent record. i.e. in my case Project is the Child entity and will be hosting the embedded canvas app and Opportunity is the Parent Entity. On the canvas app when i insert a edit form, i automatically get a list of fields from the Project entity, but dont have an option to add Opportunity fields, hence i will have to tweak the Project entity fields and point them to Opportunity (Still figuring out how).
2) Start with a blank edit form and add all the fields along with their data type and then figure out a way to populate the fields on load and then store the fields values as those are edited on some collection and save it when submit button is pressed using patch function.

In both the cases i would add two data sources i.e. Project and Opportunity tables from Dataverse.

Was this reply helpful? Yes No