Form Component Control can be used to update the parent record -through Debajit’s blog post, we came to know about it- https://debajmecrm.com/how-to-edit-a-parent-record-from-child-record-form-in-dynamics-365-dataverse/
Below is our custom entity/table named Sample Entity having contact’s lookup.
Let us add one more contact field, specify the Form Component control for it
We need to specify the main form to be used as a static value within the QuckForms tag.
entityname will be the schema name of the entity and the id of the main form.
Get the form id in the classic form editor –
And in the new form designer –
Save and publish the change.
We can see the main form of the contact being rendered within the custom entity’s form on the selection of Contact lookup value.
Now let us look at the some of the key points –
- Only the Main form can be considered while using form component control i.e. only the main form can have the form component control which must be the main form itself. Quick View, Quick Create, and card cannot be used.
- The form component will only show the first tab of the form. Below is the form we have configured, but it shows only the summary tab.
- The validation of the embedded parent form still applies as shown below.
- Data is sent for save independently for each record, which has no defined order.
- It is not recommended to use the form with Business Process Flow as a form component.
- Form components cannot have another main form with form components embedded in them. Although we do not get any error, it might be unsupported.
- The same form can be used across different form components but is not supported as per Microsoft Docs. Here we have embedded the same form inside Account’s form.
Get all the details here
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/form-component-control
Hope it helps..
Nishant Rana's Weblog 
I am not able to view the Form component Control in CRM. How can I get that ?
LikeLike
Hi Nishant – We have been using this for some time but have started to notice that they don’t always load and you get the default form shown for the related parent entity. If you refresh the page it then renders. A quick check behind the scenes via Dev Tools and we are seeing a failed promise. Have you come across this when you are using it? We have raised a support case with Microsoft as well but still waiting a response.
LikeLike
Hi Tom hope you are doing well. Thanks for reading the article and sharing your experience. Unfortunately we haven’t used it any of our projects so have not faced that issue. Clearly seems like some product bug.
LikeLike
Hi Nishant,
Do you by any chance know whether this form component control can be dynamically manipulated through javascript? Especially, for my use case, the id of the form to use. If yes, can you point me to the reference on that? I did not find it…
LikeLike
Little correction :
The “Form Componant Control” (FCC) will show not the first tab, but the “active” tab having the focus, either defined at design time or selected via javascript/typescript. In our case, some bussiness logic at the open event of the form selects the “active” tab of the form. When the form is displayed using the FCC, the “active” tab is shown, not the first.
FCC is a fantastic improvement in D365 to avoid the user to click to see details and after having to navigate back to previous form… Users HATE to switch “context”.
LikeLike
Hi, how to use the Form component control in Java script ? Thanks in advance
LikeLike