Ask: As a customer we think the current limitations of the Form Component Control could be improved allowing embedding the Contact form into the Opportunity form using the Form Component Control. Please keep us posted if the behavior/limitations for the editable Form Component Control are updated or if a fix becomes available—we’re happy to validate when it ships.

Symptom: You are experiencing a 'Record is Unavailable' error with error code -2147220969 when attempting to change stages on a custom Opportunity Business Process Flow (BPF) in Dynamics 365 Sales.

Summary: For your case we had meeting to review the issue and collected needed details including a Support Instance. We escalated this issue to our product team and also reviewed it internally with my team. Based on the evidence provided, we confirmed the behavior is linked to the use of the editable Form Component Control, specifically when embedding the Contact form into the Opportunity form. As you noted, removing the editable quick view allows the Business Process Flow (BPF) to function correctly. This behavior is a platform limitation of the Form Component Control. Microsoft has documented several constraints associated with this control, particularly when used in editable mode. For your reference, here are some official documentation links outlining these limitations:

Limitations

Note the following limitations when you add the form component control to a table form:

• The form component control only supports rendering main forms. Similarly, support for adding a form component control is only supported with main forms. Other form types, such as quick create, quick view, and card aren't supported.
• Forms with a business process flow aren’t currently supported in either the main table form or the related table form. If you have a form with a business process flow, you might encounter unexpected behavior. We recommend that you don't use a form component with a form that uses a business process flow.
• The form component control doesn't support embedded form component controls, such as adding a form component control to a form that is used by a form component control.
• The form component control doesn't support embedded canvas apps. You might encounter unexpected behavior with these canvas apps.
• The form component control will only display the first tab of the form it uses if multiple tabs are included in that form.
• Using the same form for different form component controls on a single form isn't supported.
• The form that you use with a form component must be included in your app. If it isn't, or if the current user doesn't have access to the form, it falls back to the top-most main form that is included in the app and available to the user (based on form order).
• All components used by the form in a form component must be included in your app. These components include related tables, views, and business process flows. If they aren't, they won't be available in the form or there might be unexpected behavior.
• Form component controls have certain limitations when rendered in multi-session apps. Specifically, dynamically added handlers on the form component form such as addOnSave or addOnChange might not run after switching multisession tabs.
• You might notice that the timeline wall might not update when a column that is used to set the timeline wall has changed in the form component. When the page is refreshed the timeline wall updates as expected.
• On mobile, the timeline control doesn't currently appear in the form component control.
• For subgrids, the See associated records command button won't be available if the subgrid is rendered inside a form component.
• Form component controls aren't supported in bulk edit dialogs. They won't appear in the form in the bulk edit dialog by default and any changes made to related table records with them won't be saved.
• When duplicate records are detected when a form component control is saved, users might not be able to view the duplicates to resolve conflicts.
• Form validation only happens for the required fields that are rendered. Validation isn't possible for required fields that aren't visible or not rendered or present on another tab.

• Data in quick view form controls can't be edited and they do not support form scripts.
• Because quick view forms are viewed using a quick view control in a form, they do not include header, footer, or navigation areas. Security roles can't be assigned to quick view forms and they can't be activated or deactivated.
• Custom controls aren't supported in quick view forms, and there is limited customization support for complex controls such as subgrids. If this is required, consider using a Form component control

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-edit-quick-view-forms

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/form-component-control#limitations

Resolution: You replaced the editable Quick View (Form Component Control) on the Opportunity form with a standard (read-only) Quick View. After this change, the BPF stage transitions work correctly and the error no longer reproduces.