> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/update-record.md).
# Change Data Record
## Description
The Change Data Record part allows application users to update a record in a table.
**Node Type:** This part is located in a process node.
**Used With:** This part can be used with all frameworks as well as with projects not based on a framework.
## Use
The update record part can be used to update data in a resource data table by choosing a data source. Based on the selection and column configuration it is possible to update one or more columns and rows.
## Editor Fields
| Tab | Field Name | Description/Use | Type/Options | Optional/Mandatory |
| -------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Basic | Data source | This is the name of the resource data table in which you want to change/update data. | Table | Mandatory |
| Basic | Selection | Once you have selected a data source the system displays the Selection Editor, which allows you to specify which data you want to use from your resource data table. By defining the selection criteria, you can limit the data you want to use or display to your users.
The selection operators the system displays vary based on the variable type:
- Numeric Fields: equals, not equals, is larger (or equal) than, is smaller (or equal) than, in, not in
- Text Fields: equals, not equals, is not, like, equals or empty, in, not in
You can also use "like" with leading and/or trailing wildcard (%), if necessary.
If your variable is a text, quoted, or comma-separated collection you can use in and not in. Use the format variable part to do the conversion. If the collection is empty, the system will drop this term from the query to avoid an error from "where target in {null}."
You can build complex criteria using the editor by using AND/OR (toggle to switch) and adding parentheses around specific terms to define the precise selection rules.
Advanced Note: While less-commonly used, you can also apply the greater than/smaller than rules for numeric fields using SQL.
| Statement | Optional |
| Basic | Columns | In the Selection Editor, the Columns row identifies the name of the columns you want to update. The Data Object row identifies the data objects with which you want to update the columns in the table.
Click the ... button to automatically load all the existing columns from the selected data source table.
| Table | Mandatory |
| Basic | Log data object | This is the name of the data object that stores error messages from the execution of the database parts: add data record, get data record, update data record, delete data record, and import values. If you specify a log data object, the system stores error message and a stack trace of the database part to this data object.
When used by multiple database parts, the Log data object stores the cumulative list of error messages from the different parts.
| Text | Optional |
| Basic | Reset log data object | When you check this field, the system clears the error messages from the Log data object. Typically, this option should be checked in the first database part of a sequence of database parts. | Checkbox | Optional |
| Basic | Skip on error | When you check this field the system skips the execution of subsequent database parts linked to the same Log data object. | Checkbox | Optional |
| Advanced | Database | This is the name of the database if the data is not stored in the same project and when the data location cannot be retrieved automatically. | Text | Optional |
## Examples
Please download and import one of the following [example projects](/release-9/example-gallery/example-projects-for-parts/update-record-example-project.md) in your workspace.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/update-record.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.