> 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/9.3-data-integration/pdi-transformation-steps-reference-overview/add-sequence-step-article/pdi-transformation-counter-generated-sequence-add-sequence-step.md).

# PDI transformation counter generated sequence

![Use a transformation counter to generate the sequence](/files/5UXpIBO7016TL8jsmWaD)

The following table contains options for generating a sequence from a PDI transformation counter:

| Option                                 | Description                                                                                                                                                                                                                 |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Use counter to calculate sequence?** | <p>Select this check box if you want the sequence to be generated by PDI. This option is set by default</p><p><strong>Use DB to generate the sequence?</strong> is automatically selected if this check box is cleared.</p> |
| **Counter name (optional)**            | Specify the name of the counter if multiple steps in a transformation generate the same value name to avoid unique sequencing across multiple steps.                                                                        |
| **Start at value**                     | Specify the value to start the sequence. For example, if **Start at value** is set to `1`, then the sequence will start with `1`. If **Start at value** is set to `0`, then the sequence will start with `0`.               |
| **Increment by**                       | Specify the amount by which the sequence increases or decreases.                                                                                                                                                            |
| **Maximum value**                      | Specify the value to reach before returning the sequence to the **Start at value** setting.                                                                                                                                 |

For example, if you set \*\*Start at value\*\* to \`1\`, \*\*Increment by\*\* to \`1\`, and \*\*Maximum value\*\* to \`3\`, then the resulting sequence will be \`1, 2, 3, 1, 2, 3, 1, 2\`... If you set \*\*Start at value\*\* to \`0\`, \*\*Increment by\*\* to \`-1\`, and \*\*Maximum value\*\* to \`-2\`, then the resulting sequence will be \`0, -1, -2, 0, -1, -2, 0\`...


---

# 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://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/add-sequence-step-article/pdi-transformation-counter-generated-sequence-add-sequence-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.