You plan to create a Microsoft Power Apps Component Framework (PCF) code component for a record form in a model-driven app. The code must be able to read the record's Id column. You need to…

Question

Options

• Aresources
• Bproperty
• Cfeature-usage
• Dtype-group

• A
  4% (1)
• B
  88% (22)
• C
  4% (1)
• D
  4% (1)

Explanation

Option B (property) is correct because the PCF manifest <property> element is how you declare the data bindings your component needs - including special "bound" properties like the record Id. To expose the record Id, you define a property with of-type="SingleLine.Text" and bind it to the form's primary key column, making it accessible in your component's TypeScript code via the context.parameters object.

Why the distractors are wrong:

• A (resources) - declares static assets your component needs (CSS, JS libraries, etc.), not data bindings.
• C (feature-usage) - declares which PCF framework features (e.g., Device API, WebAPI) your component will use; it has nothing to do with reading column values.
• D (type-group) - creates a named alias for a set of compatible data types, used to constrain property types, but doesn't itself expose any column data.

Memory tip: Think of property as the component's "data contract" with the form - if you need to read or write any column value (including the Id), you must declare it as a <property> in the manifest. Everything else (resources, features, type groups) is configuration scaffolding, not data access.

No community discussion yet for this question.