> For the complete documentation index, see [llms.txt](https://readme.directual.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.directual.com/scenarios/editing-scenarios/action-steps/edit-object-step.md).

# Edit object step

![](/files/-MVtt1Lk8yuhDroAeilo)

**Edit object** step allows you to edit current object and objects connected with it via links.

![](/files/-MVtsj-isTsaHl7yfdXI)

{% hint style="info" %}
Remember! You cannot combine **serial actions** with the same field in a single step. You have to create step-by-step chain. It means if you want to increase {{field}} to 5, and then divide it by 10, you should create two separate steps for {{field}} + 5, and then in the second step {{field}} / 10 (don't forget to turn on [evaluating the expression](/template-system/evaluating-as-js-expression.md) for such calculations).
{% endhint %}

## Basic step settings

There can be several fields editing, each includes:

* The field to edit ([select field](/template-system/basics-of-template-system.md#inputs-for-templating));
* The value ([expression](/template-system/basics-of-template-system.md#inputs-for-templating)) – here you can apply JS-interpreter.

## Advanced step settings

### Single-thread execution (lock)

The way to avoid collisions while writing to the same field. 

* Lock key (field type of link like `{{userID}}` or `{{ContextVar.userID}}`);
* Time of lock in milliseconds;
* Global lock option (cross-scenario setting)

### Generation of an event

Following the [event model](/scenarios/principles-of-scenarios/directual-event-model.md), editing an object can trigger other scenarios. By default, this step edits an object in "silence mode", but you can turn on the event generation. 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://readme.directual.com/scenarios/editing-scenarios/action-steps/edit-object-step.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.