Sequence: Business Rule Actions for Account Main Form Drop-Down
DRAG DROP
A company is using the Account table and a main form named Account Main.
The company defines the following requirements for the Account Main form:
• Evaluate a single value selected as part of a drop-down list.
• Display a message and suggestion based on business intelligence if the drop-down list value equals a specific value.
• Logic must run against this form only.
You need to implement the logic.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.
Community Insight
The question tests form-scoped business rule creation with a Recommendation action; the trap is choosing a Cloud Flow or setting scope to the whole entity instead of the specific form.
For model-driven app form-level logic in Power Platform, a business rule scoped to a specific main form (Account Main) with a Recommendation action lets you evaluate a choices (drop-down) column and surface guidance. The correct sequence is: create the choices column, create the business rule, set its scope to the Account Main form, then add a recommendation action.
The most common wrong approach is building a cloud flow or Power Fx command instead of a business rule, or creating a business rule with Entity scope (all forms) when the requirement explicitly says the logic must run against the Account Main form only.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The requirements map directly to a model-driven app business rule: you first need the drop-down field itself, so creating a choices column on the Account table is the prerequisite step. You then create a business rule on the Account table, and because the logic must run against the Account Main form only, you set the rule's scope to that specific form (form-level scope) rather than the whole entity. Finally, the requirement to "display a message and suggestion based on business intelligence" is satisfied by a Recommendation action inside the rule, which shows a recommendation message with a suggested field action. The sequence column → business rule → form scope → recommendation action is the only ordering that satisfies every stated requirement in dependency order.Why Other Candidate Answers Are Wrong
Any ordering that places the recommendation action before the business rule is invalid, because a Recommendation action is a component that lives inside an already-created and scoped rule. Choosing a Cloud Flow, a Power Automate approval, or JavaScript on the form's onLoad event fails the "evaluate a single selected drop-down value and display guidance" pattern that business rules are designed for, and unnecessary server-side components introduce latency. Setting the rule's scope to the entire Account entity (all forms and the API) contradicts the explicit constraint that the logic run on this form only, and would also make the rule harder to maintain. Omitting the choices column step is impossible, since the rule has no field to evaluate until that column exists.Community Comment Notes
A single community comment laid out the same order: "1. Create a choices column 2. Create a business rule 3. Set scope to Account Main Form 4. Add a recommendation action." That matches the vendor's documented business rule workflow, where the scope and the rule action type are configured after the rule is created on the table, so the comment is consistent with the correct answer.Official Reference
Exam Strategy
When a drag-drop asks for a sequence on a model-driven main form, look for the prerequisite data element (the choices column) first, then the container (business rule), then its scope, then the specific action type. Words like "message and suggestion" are the signature of a Recommendation action, while "run against this form only" means form-level scope, not entity scope.
Frequently Asked Questions
Why set a business rule scope to a specific form instead of the whole Account table?
Entity scope runs the rule on all forms, views, and the Web API, while a form scope runs only on the selected form—matching the requirement that logic run against the Account Main form only.
Which business rule action displays a message and suggestion for a chosen field value?
The Recommendation action: it shows a recommendation message and a suggested action on the form when the trigger condition (for example, a drop-down value) is met.