Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Add page action Enabled false-positive guard

Browse source 
Document that an OnAction trigger need not duplicate a TestField check when the action's Enabled expression already prevents UI invocation with the field blank.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
wenjiefan 2026-08-17 11:27:41 +02:00
parent 91f52f8b4f
commit 198dbd8d59
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
microsoft/knowledge/error-handling/enabled-action-need-not-repeat-testfield.md Normal file
View file

@ -0,0 +1,22 @@
---
bc-version: [all]
domain: error-handling
keywords: [page-action, onaction, enabled-expression, testfield, mandatory-field, ui-validation, false-positive]
technologies: [al]
countries: [w1]
application-area: [all]
---
# An enabled expression can make a repeated TestField unnecessary in OnAction
## Description
A page action's `Enabled` expression controls whether the user can invoke its `OnAction` trigger. When that expression requires a record field to be nonblank, the UI cannot invoke the action while the field is blank. Repeating the same presence check with `TestField` at the start of `OnAction` is therefore not required for that UI path.
## Best Practice
Do not flag a missing `TestField` in `OnAction` when the action's `Enabled` expression already proves that the same field is nonblank before UI invocation. Require validation in shared business logic or other entry points that do not have the action's UI guard.
## Anti Pattern
Recommending an unconditional duplicate `TestField` solely because `OnAction` uses the field, without accounting for an `Enabled` expression that prevents invocation while the field is blank.