> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/reference/workflows/transforms/step-rename.md). # Step: Rename ## Overview The **Rename** step changes the name of an existing variable. #### Example starting data: ``` /*---------+--------*  | student | score |  +---------+--------+  | jane    | 83 |  | neal    | 35 |  | sam | 74 |  | pat | 62 |  *---------+--------*/ ``` #### Example output data: Rename `score` to `final_score` ``` /*---------+--------------*  | student | final_score |  +---------+--------------+  | jane    | 83 |  | neal    | 35 |  | sam | 74 |  | pat | 62 |  *---------+--------------*/ ``` ## Step structure
* There will be at least one rename block where you define a variable and a new name. ## Input field definitions
FieldDefinition
Source variableThe variable that you want to rename.
New nameThe name that your selected source variable will be given.

Note that this input needs to follow Redivis variable naming constraints.
## Example We can change the name of a variable to give more meaning to the data. #### Starting data: ``` /*---------+-------+---------+------------*  | test | score | student | date |  +---------+-------+---------+------------+  | quiz    | 83    | jane    | 2020-04-01 |  | quiz    | 35    | pat     | 2020-04-01 |  | quiz    | 89    | sam     | 2020-04-01 |  | midterm | 74   | jane    | 2020-05-01 |  | midterm | 62    | pat    | 2020-05-01 |  | midterm | 100  | sam     | 2020-05-01 |  | final   | 77    | jane    | 2020-06-01 |  | final   | 59   | pat     | 2020-06-01 |  | final   | 100  | sam     | 2020-06-01 |  *---------+-------+---------+------------*/ ``` #### Input fields:
* **Source variable:** The variable we want to rename is `date` so we select that here. * **New name:** `date_taken` would be a better name for this variable, so we enter it here. #### Output data: ``` /*---------+-------+---------+------------*  | test | score | student | date_taken |  +---------+-------+---------+------------+  | quiz    | 83    | jane    | 2020-04-01 |  | quiz    | 35    | pat     | 2020-04-01 |  | quiz    | 89    | sam     | 2020-04-01 |  | midterm | 74   | jane    | 2020-05-01 |  | midterm | 62    | pat    | 2020-05-01 |  | midterm | 100  | sam     | 2020-05-01 |  | final   | 77    | jane    | 2020-06-01 |  | final   | 59   | pat     | 2020-06-01 |  | final   | 100  | sam     | 2020-06-01 |  *---------+-------+---------+------------*/ ``` --- # 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://docs.redivis.com/reference/workflows/transforms/step-rename.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.