> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/pdi-transformation-steps-reference-overview/set-field-value-to-a-constant.md).

# Set Field Value to a Constant

The Set Field Value to a Constant step replaces the value of a field with a constant value you define.

### General

| Field                        | Description                                                                                               |
| ---------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Step name**                | Specify the unique name of the step on the canvas. You can customize the name or leave it as the default. |
| **Use variable in constant** | Select to substitute variables inside the constant value.                                                 |

### Fields

![Set Field Value to a Constant](https://773338310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYwnJ6Fexn4LZwKRHghPK%2Fuploads%2Fgit-blob-7690e961f3f3f91b1abd70c71039e55728af4776%2FPDI_SetFieldValueConstant_Options.png?alt=media)

Use the **Fields** table to define the fields to replace.

Select **Get fields** to populate the table with fields from the incoming stream.

| Column                     | Description                                                                                                                                                     |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Field**                  | Field whose value is replaced.                                                                                                                                  |
| **Replace by value**       | Constant value used as the replacement.                                                                                                                         |
| **Conversion mask (Date)** | Date format to use when the target field is a date. See [Common Formats](/pdia-data-integration/pdi-transformation-steps-reference-overview/common-formats.md). |
| **Set empty string?**      | Set to `Y` to output an empty string when the replacement value is empty. If `N`, an empty value becomes null.                                                  |

### Metadata injection support

All fields of this step support metadata injection. You can use this step with [ETL metadata injection](/pdia-data-integration/pdi-transformation-steps-reference-overview/etl-metadata-injection.md) to pass metadata to your transformation at runtime.


---

# 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.pentaho.com/pdia-data-integration/pdi-transformation-steps-reference-overview/set-field-value-to-a-constant.md?ask=<question>&goal=<user_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.