You are creating a cloud flow for an automation targeting Dataverse. When a new account is created in Dataverse, the name of the account must be updated based on the following logic: - If the…

Question

Options

• Aif(equals(triggerOutputs()?['body/accountcategorycode'), 1), concat('Standard | ',
• Bif(equals(triggerOutputs()?['body/accountcategorycode'), 2), concat('Standard ',
• Cif(equals(outputs('trigger')?['body/accountcategorycode'], 1), concat('Standard | ',
• Dif(equalsfoutputs('trigger')body/accountcategorycode'], 2), concat('Standard | ',

• A
  73% (24)
• B
  3% (1)
• C
  9% (3)
• D
  15% (5)

Explanation

The correct formula must satisfy two requirements: use the proper Power Automate expression syntax for accessing trigger outputs, and compare against the value 1 (Preferred Customer) as the primary condition. In Power Automate cloud flows triggered by Dataverse, the correct function to access trigger body fields is triggerOutputs()?['body/fieldname'] - NOT outputs('trigger')?['body/fieldname']. This eliminates choices C and D, which use incorrect syntax. Between A and B, the logic dictates checking for value 1 first (Preferred Customer → prepend 'Preferred | '), with the else branch handling value 2 or null (Standard → prepend 'Standard | '). Choice B compares against 2 instead of 1, which reverses the logic incorrectly. Choice A uses the correct triggerOutputs() function and checks for equality with 1, making the if-true branch handle the Preferred Customer case and the if-false branch (truncated in the choices) handle the Standard/null case.

No community discussion yet for this question.