Power Platform Community Forum Thread Details

Hi Craig,

If you’re working with a model-driven app, then your approach using a Business Rule with scope = Table is correct, and it should apply.

However, the behavior you’re seeing typically comes down to how defaults are handled in Microsoft Dataverse and form rendering in Power Apps.

Why the default is not appearing on the form

Even in model-driven apps:

Business Rules do not always populate values on form load

They are triggered:
- On field change
- Or when conditions are evaluated after loa

So if your rule is simply:

“Set column value = 2”

…it may not fire immediately when creating a new record unless a trigger condition is met.

Recommended Fixes

✔ Option 1: Add a condition to force execution

Modify your Business Rule:

Condition: Field does not contain data

Action: Set field value = 2

This ensures the rule runs when the form loads for a new record.

✔ Option 2: Use Dataverse Default Value (Best Practice)

Instead of relying on a Business Rule:

Go to the column in Dataverse

Set Default Value = 2

This guarantees:

Value is set on record creation

Works across forms, APIs, and integrations

✔ Option 3: Use JavaScript (if immediate UI population is required)

If you want the value to appear instantly on form load:

function setDefaultValue(executionContext) {
var formContext = executionContext.getFormContext();
var field = formContext.getAttribute("yourcolumnname");

if (field && field.getValue() === null) {
field.setValue(2);
}
} 

Then register it on Form OnLoad.

Summary

Business Rules (Table scope) don’t always apply immediately on form load

They require a trigger condition

Best practice is to use Dataverse column default value for simple defaults

If this resolves your issue, please mark the answer as accepted and give it a like. It helps others in the community and supports knowledge sharing. Thanks!