> 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/api/rest-api/datasources/patch.md). # patch ## Overview This endpoint is used for updating information about a dataset's tables. ## HTTP Request ```http PATCH /api/v1/workflows/:workflowReference/dataSources/:dataSourceReference ``` ## Path parameters | Parameter | | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | workflowReference | A qualified reference to the workflow. See [referencing resources](/api/referencing-resources.md) for more information. | | dataSourceReference |

A qualified reference to the dataSource's current source dataset or workflow.

Alternatively, can provide the id of the dataSource.

| {% hint style="info" %} This endpoint extends the [general API structure](/api/rest-api/general-structure.md) {% endhint %} ## Request body Provide a JSON object with information about the dataSource.

Property name Type Description

Property name	Type	Description
sourceDataset	string	A qualified reference to the (new) source dataset for this dataSource. Include version / sample information in the reference to update a dataSource's version or sample status. Either a sourceDataset or sourceWorkflow must be provided, but not both.
sourceWorkflow	string	A qualified reference to the (new) source workflow for this dataSource. Either a sourceDataset or sourceWorkflow must be provided, but not both.
mappedTables	object	An object whose keys represent the current tables that are referenced on the dataSource, and whose values represent the corresponding tables in the new source dataset or workflow. E.g., `# Reference id suffixes are optional, but take precedence over names { "old_table:xje9": "new_table:a842" }` In many circumstances, tables can be automatically mapped based on their name and identifier, and this parameter isn't needed. However, if a previously-referenced table doesn't exist under the new data source – e.g., a table is deleted in subsequent versions – you'll need to provide information so that any downstream notebooks or transforms can be updates. It is only necessary to map tables that are referenced by a downstream node, not all tables associated with the dataSource.

sourceDataset

string

A qualified reference to the (new) source dataset for this dataSource.

Include version / sample information in the reference to update a dataSource's version or sample status.

Either a sourceDataset or sourceWorkflow must be provided, but not both.

sourceWorkflow

string

A qualified reference to the (new) source workflow for this dataSource.

Either a sourceDataset or sourceWorkflow must be provided, but not both.

mappedTables

object

An object whose keys represent the current tables that are referenced on the dataSource, and whose values represent the corresponding tables in the new source dataset or workflow. E.g.,

# Reference id suffixes are optional, but take precedence over names
{ "old_table:xje9": "new_table:a842" }

In many circumstances, tables can be automatically mapped based on their name and identifier, and this parameter isn't needed.

However, if a previously-referenced table doesn't exist under the new data source – e.g., a table is deleted in subsequent versions – you'll need to provide information so that any downstream notebooks or transforms can be updates.

It is only necessary to map tables that are referenced by a downstream node, not all tables associated with the dataSource.

## Authorization Edit access to the corresponding workflow is required. Your access token must have the following scope: * workflow\.write [Learn more about authorization.](/api/rest-api/authorization.md) ## Response body Returns the JSON-encoded "get" representation of a [dataSource resource](/api/resource-definitions/datasource.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 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.redivis.com/api/rest-api/datasources/patch.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.