nerdexam
Microsoft

PL-400 · Question #208

You are developing a model-driven app. The app uses data from two custom tables. The tables have a parent-child relationship. The parent record form contains a subgrid that displays the child…

The correct answer is B. Map table columns from the parent record to the child record. The correct answer is B: Map table columns from the parent record to the child record. In Dynamics 365 and Power Apps model-driven apps, relationship column mappings (configured under the relationship definition) allow you to specify that when a child record is created from a…

Submitted by takeshi77· Apr 18, 2026

Question

You are developing a model-driven app. The app uses data from two custom tables. The tables have a parent-child relationship. The parent record form contains a subgrid that displays the child records. When creating a new child record from the parent form, data must automatically populate in the child record form to reduce data input errors. You need to implement the solution. What should you do?

Options

  • AUse a Power Automate flow to read data from the parent record and update the child record upon
  • BMap table columns from the parent record to the child record.
  • CCreate a business rule that sets the default values on the child record fields to values from the
  • DInclude a quick view form on the child record showing the data from the parent record.

How the community answered

(21 responses)
  • A
    10% (2)
  • B
    86% (18)
  • C
    5% (1)

Explanation

The correct answer is B: Map table columns from the parent record to the child record. In Dynamics 365 and Power Apps model-driven apps, relationship column mappings (configured under the relationship definition) allow you to specify that when a child record is created from a parent record's subgrid, certain parent field values are automatically copied into the corresponding child record fields. This is a native, no-code platform feature that fulfills the requirement of auto-populating child record data to reduce input errors. A Power Automate flow (A) would fire after the record is created, not at form open time, so the fields wouldn't pre-populate before saving. A business rule (C) can set default values but cannot dynamically pull values from a specific parent record without custom scripting. A quick view form (D) displays parent data on the child form read-only but does not populate editable child fields.

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice