nerdexam
Microsoft

PL-200 · Question #261

You have a classic workflow. The workflow updates a custom column on a record when an account record is created. The workflow must update the custom column based on the following conditions…

The correct answer is C. Add the two columns with the default value by using the Forms Assistant. C – Add the two columns with the default value by using the Forms Assistant is the correct answer. In classic Dataverse workflows, the Forms Assistant (accessed when setting a field value in an Update Record step) allows you to chain multiple dynamic values in a fallback…

Configure Microsoft Dataverse

Question

You have a classic workflow. The workflow updates a custom column on a record when an account record is created. The workflow must update the custom column based on the following conditions: - Update the custom column value using the Account Number. - If the Account Number column is blank, update the custom column value using the Ticker Symbol. - If the Ticker Symbol column is blank, update the custom column value to N/A. You need to configure the custom column value by using the update record step. What should you do?

Options

  • AAdd a formula that evaluates the two column values and uses the first populated value or else the
  • BAdd an expression that evaluates the two column values and uses the first populated value or
  • CAdd the two columns with the default value by using the Forms Assistant.
  • DAdd check conditions to determine if the two columns contain data.

How the community answered

(53 responses)
  • A
    11% (6)
  • B
    2% (1)
  • C
    83% (44)
  • D
    4% (2)

Explanation

C – Add the two columns with the default value by using the Forms Assistant is the correct answer.

In classic Dataverse workflows, the Forms Assistant (accessed when setting a field value in an Update Record step) allows you to chain multiple dynamic values in a fallback (coalesce) pattern - all within a single update step, without needing separate condition branches. You specify:

  1. Account Number field (used if not blank)
  2. Ticker Symbol field (used if Account Number is blank)
  3. The static text "N/A" (used if Ticker Symbol is also blank)

The Forms Assistant evaluates each value in order and uses the first non-empty result, matching all three requirements in one configuration.

Why the others are wrong:

  • A – Add a formula: Classic workflows do not use formulas (that is a Power Fx/canvas app concept). The Forms Assistant is the correct tool, not a formula editor.
  • B – Add an expression: Expressions in this sense belong to Power Automate cloud flows, not classic background workflows. Classic workflows use the Forms Assistant for dynamic values.
  • D – Add check conditions: While you could build this logic using separate condition branches (If Account Number is blank → check Ticker Symbol → etc.), that approach is more complex and redundant. The Forms Assistant handles this coalesce pattern natively in a single step, making D an unnecessarily complicated alternative.

Topics

#Classic Workflow#Dataverse#Forms Assistant#Conditional Logic

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-200 Practice