Override Internal Datasource Value

The Override Internal Datasource Value action is used to replace an existing value inside an Internal Datasource with a new one.

This action only works on top-level keys and object properties.

You cannot delete a specific value inside an array.

When to Use

Use this action when you need to replace a value with one that comes from a sensor, static definition, widget, or another runtime source.

Common use cases include:

• Resetting or updating a value during user interaction
• Dynamically assigning a sensor or input result
• Saving user input for later use

Requirements

The Editable From Display setting must be enabled on the Internal Datasource.

Learn more: Alternative Datasource Settings

Action Behavior

• Replace the targeted value with a new one.
• The new value can be dynamically chosen from trigger data, a fixed constant, or extracted from a property.

Configuration Options

Field	Description
Datasource	The Internal Datasource path to the value you want to override.
Value Origin	Selector to choose where the replacement value comes from.

Value Origin Options

Type	Description
Received Value	The primary value received from the trigger. Usually refers to the value field.
Static Value	A constant, hardcoded value.
Property of Received Value	Extracts a specific property from the full trigger object (e.g., event, id, or value). Supports dot notation for accessing nested values (e.g., value.payload.amount).

Example

If your Internal Datasource looks like this:

{
    "status": "waiting",
    "code": 0
}

And you run an Override action on path status using a static value of "done", the result will be:

{
    "status": "done",
    "code": 0
}

Usage in Action Batches

Like all other Internal Datasource actions, you can use this one inside an Execute Action Batch and combine it with Evaluations or conditions.