Skip to content

Commit 7f8112a

Browse files
authored
Formatting changes
1 parent cf30ca9 commit 7f8112a

File tree

1 file changed

+3
-3
lines changed
  • powerapps-docs/developer/component-framework

1 file changed

+3
-3
lines changed

powerapps-docs/developer/component-framework/faq.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
author: ghurlman
66
ms.service: powerapps
77
ms.search.keywords:
8-
ms.date: 12/10/2020
8+
ms.date: 06/03/2021
99
ms.author: grhurl
1010
ms.reviewer: nabuthuk
1111
title: Power Apps component framework FAQs
@@ -64,9 +64,9 @@ sections:
6464
answer: |
6565
To add commandbar, search to a subgrid for model-driven apps, you need to specify the [cds-data-set-options](manifest-schema-reference/data-set.md).
6666
67-
- question: Can I access the form context like I can in model-app event handlers?
67+
- question: Can I access form context like I can in model-driven apps event handlers?
6868
answer: |
69-
Accessing the form context directly in a control is not supported. Code components are expected to work across various platforms and surfaces like model-driven apps, canvas apps, and dashboards, and hence they cannot take dependency on form context. A work around is to make a control bound to a field and add an OnChange event handler to that field. The control can update the field value, and the OnChange event handler can access the form context. A field not bound to an entity could be used, or a field bound to an entity with submitMode set to "never" could be used. We will add support for the custom events in future which can be used for communicating changes outside of a control without adding a field configuration.
69+
Accessing form context directly in a control is not supported. Code components are expected to work across various products like model-driven apps, canvas apps, dashboards, and hence they cannot have dependency on the form context. A work around is to make the code component bound to a column and add an `OnChange` event handler to that column. The code component can update the column value, and the `OnChange` event handler can access the form context. Column not bound to a table could be used, or a column bound to a table with `submitMode` set to `never` can be used. We will add support for the custom events in future which can be used for communicating changes outside of a control without adding a column configuration.
7070
7171
additionalContent: |
7272
## See also

0 commit comments

Comments
 (0)