Two business rules setting the same column

Business rules set the same column with no documented order.

Two or more active business rules on one table set the same column, and their scopes overlap. Microsoft documents no evaluation order for business rules on the same table, so where both act on a row, the stored value rests on no published contract.

Scope decides where a rule runs: a rule scoped to the whole table runs on every form and on the server when a row is saved, and a rule scoped to a form runs only while that form is open. Pathix reports a whole-table rule against any other rule on the table, and two form-scoped rules only when they are bound to the same form. Only Set column value counts: showing, hiding, locking or defaulting a column changes the form, not the stored row. Deactivated rules are not compared, a step whose column could not be resolved is left out rather than guessed, and because each step usually sits under a condition, the finding reports that both rules can set the column, not that both do.

Open each active business rule on the table and list the columns its Set column value steps write, with the rule's scope. Any column set by two rules whose scopes overlap is the finding: a whole-table rule overlaps every other rule, and two form-scoped rules overlap when they are bound to the same form.

Decide which rule owns the column and remove the Set column value step from the others, or merge the logic into one rule.

This one is environment health, so it carries a plain label and no control mapping. Presenting an operational gap as a security finding would make the real security findings harder to trust, so we keep the two apart.

• A plugin step that re-triggers itself on every save
• A cloud flow that re-triggers itself on every run
• Two plugin steps at the same execution order writing one column
• Two flows writing the same column on the same trigger