> 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/archived-merged-pages/working-with-transformations-archive/edit-transformation-properties.md).
# Edit transformation properties
#### Dependencies tab
Use the **Dependencies** tab to specify all of the dependencies for the transformation.The **Dependencies** tab allows you to enter all of the dependencies for the transformation. For example, if a dimension depends on three lookup tables, make sure that the lookup tables have not changed. If the values in these lookup tables have changed, extend the date range to force a full refresh of the dimension.Dependencies allow you to determine if a table has changed when you have a "data last changed" column in the table. Click **Get dependencies** to detect dependencies automatically.
| | |
| ---------- | ------------------------------------------------------------------------------------------------- |
| Connection | A dropdown to select a database connection that has already been created for that transformation. |
| Table | A specific table from the selected database connection. |
| Field | A specific field within the selected table. |
#### Miscellaneous tab
Use the **Miscellaneous** tab to configure buffer and feedback size and performing various administrative tasks.This tab includes the following options:
| | |
| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Number of rows in rowset | Allows you to change the size of the buffers between the connected steps in a transformation. Do not change this parameter unless you are running low on memory, for example. |
| Show a feedback row in transformation steps? | Controls whether or not to add a feedback entry into the log file while the transformation is being executed. By default, this feature is enabled and configured to display a feedback record every 5000 rows. |
| The feedback size | Sets the number of rows to process before entering a feedback entry into the log. Set this higher when processing large amounts of data to reduce the amount of information in the log file. |
| Make the transformation database transactional | This allows you to open one unique connection per defined and used database connection in the transformation. Enabling this option is required to allow a failed transformation to be completely rolled back.Enabling this option is also necessary when trying to alter connection settings before a query using an "Execute SQL script" step. (See also the **Advanced** section in the Database Connection dialog box "Enter the SQL statements (separated ...) to execute right after connecting")Further information can be found in [Database transactions in jobs and transformations](https://pentaho-public.atlassian.net/wiki/spaces/EAI/pages/386803253/Database+transactions+in+jobs+and+transformations).**Note:** A transformation wide commit for all steps is done when the last step finishes. When the transformation fails, a rollback is done. It is not necessary to set any commit sizes since they are ignored. |
| Shared objects file | Specifies the location of the XML file used to store shared objects like database connections, clustering schemas, and more. |
| Manage thread priorities? | Allows you to enable or disable the internal logic for changing the Java thread priorities based on the number of input and output rows in the "rowset" buffers. This can be useful in some situations where the cost of using the logic exceeds the benefit of the thread prioritization. |
#### Monitoring tab
Use the **Monitoring** tab for enabling and disabling step performance monitoring and setting related performance parameters.This tab includes the following options:
| | |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable step performance monitoring? | This activates performance monitoring for transformation steps. It shows how many rows of data are being written, read, inputted, or outputted for each step. These metrics can be viewed on the **Performance Graph** tab that’s part of the **Execution Results** panel below the canvas. |
| Step performance measurement interval (ms) | This is the interval in milliseconds used to take a snapshot. Example: 10 ms |
| Maximum number of snapshots in memory | Sets the maximum number of measurement snapshots that can be held in memory during 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 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/archived-merged-pages/working-with-transformations-archive/edit-transformation-properties.md?ask=&goal=
```
`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.