---
title: Update Datasource
description: Update records in a selected datasource table using previous activity output.
category: Infoveave activities
tags: [update, datasource, writeback, integration, ETL]
---

# Update Datasource

## Description

The **Update Datasource** activity updates existing records in a specified table of a connected datasource using the tabular output of a previous activity. It uses user-defined **Key Columns** to locate the records and applies transformations as defined in the **Column Map**.

This is typically used for write-back operations after transforming or enriching data during a workflow. Only matching records in the target datasource will be updated.

> **Use case**:  
> After applying data cleansing or enrichment transformations in a workflow, use this activity to push the updated data back to the original datasource, e.g., updating a SQL table or spreadsheet with corrected values.

---

## Input

| Input Type | Format | Description                                     |
| ---------- | ------ | ----------------------------------------------- |
| **Data**   | Table  | Transformed data to be used for record updates. |

---

## Output

| Output Type | Format | Description                                       |
| ----------- | ------ | ------------------------------------------------- |
| **Data**    | Table  | Resulting data after update operation is applied. |

---

## Configuration Fields

| Field Name      | Description                                                             |
| --------------- | ----------------------------------------------------------------------- |
| **Datasource**  | Required. The datasource connection where the update will be performed. |
| **Table**       | Required. Table within the selected datasource to update.               |
| **Key Columns** | Required. Columns used to uniquely identify which records to update.    |
| **Column Map**  | Required. Maps input data columns to target datasource columns.         |

---

## Sample Input

_(Data is passed from a previous activity, such as a transformation or filtering step.)_

| CustomerID | Status   | LastUpdated       |
| ---------- | -------- | ----------------- |
| C001       | Active   | 2024-07-01T10:00Z |
| C002       | Inactive | 2024-07-01T11:15Z |

---

## Sample Configuration

| Field       | Value                                                              |
| ----------- | ------------------------------------------------------------------ |
| Datasource  | `SalesDB`                                                          |
| Table       | `Customer_Status`                                                  |
| Key Columns | `CustomerID`                                                       |
| Column Map  | <ul><li>Status → Status</li><li>LastUpdated → Updated_At</li></ul> |

---

## Sample Output

| CustomerID | Status   | Updated_At        |
| ---------- | -------- | ----------------- |
| C001       | Active   | 2024-07-01T10:00Z |
| C002       | Inactive | 2024-07-01T11:15Z |