> 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/pentaho-data-mastering/transforming-suggested-row-records-into-master-records.md).

# Transforming Suggested Row Records into Master Records

Transform Suggested Row Records into Master Records so that those Master Records can be transformed into Golden Records. Records in the Suggested Row Records table were not automatically transformed into Master Records due to match or merge conflicts or missing key column values. A record in the Suggested Rows table cannot be edited until that record is transformed into a Master Record.

You must have **data steward** privileges to transform a Suggested Row Record into a Master Record.

Data stewards can transform a Suggested Row Record into a Master Record in the following ways:

* [Transforming a single Suggested Row Record into a single Master Record](https://docs.pentaho.com/pentaho-data-mastering/transforming-suggested-row-records-into-master-records/transforming-a-single-suggested-row-record-into-a-single-master-record.md)
* [Transforming multiple Suggested Row Records into a single Master Record](https://docs.pentaho.com/pentaho-data-mastering/transforming-suggested-row-records-into-master-records/transforming-multiple-suggested-row-records-into-a-single-master-record.md)
* [Transforming multiple Suggested Row Records into multiple Master Records](https://docs.pentaho.com/pentaho-data-mastering/transforming-suggested-row-records-into-master-records/transforming-multiple-suggested-row-records-into-multiple-master-records.md)


---

# 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/pentaho-data-mastering/transforming-suggested-row-records-into-master-records.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.
