You create a business rule on contact entity to enforce the requirement that users must enter either a telephone number, fax number, or an email when…

To update an active business rule in Microsoft Dataverse, it must first be made inactive. There are two primary methods to achieve this goal.

The first method is to create a copy of the rule. The copy is created in a draft (inactive) state, allowing for safe modification of its conditions. After the changes are validated, the new rule is activated, and the original rule is deactivated and deleted to avoid conflicts.

The second, more direct method is to deactivate the existing rule, modify its condition as required, and then reactivate it. Option D, "Change the condition and activate the change," is a high-level summary of this direct process, as changing an active rule necessitates deactivation first, and activation is required to make the change effective.

B. This process is incomplete. While deactivating and changing the rule are necessary steps, the rule is left in an inactive state and will not be applied to records.

C. Taking a snapshot of a business rule is a feature used to convert its logic into a real-time workflow (a process), not for editing the rule itself.

1. Microsoft Learn. "Create business rules and recommendations to apply logic in a model-driven app form."

Section: Edit a business rule

Content: "When you want to change a business rule

you must deactivate it before you can edit it... 3. On the command bar

select Deactivate... 4. Make the changes that you want to the business rule... 5. When you are finished with your changes

on the command bar

select Activate." This documentation confirms the Deactivate -> Edit -> Activate lifecycle

which is summarized in option D as a complete action.

2. Microsoft Learn. "Create a business rule for a table."

Section: Edit a business rule

Content: "To modify an existing business rule

you must first deactivate it." This reinforces that direct editing of an active rule is not possible and that deactivation is a mandatory first step

which is implicitly part of the process described in option D. The documentation for the classic interface also describes a "Save As" function

which supports the copy-and-replace methodology described in option A.