Sigma Input & Write-Back Tables 

In most analytics environments, users typically consume data that originates from data warehouses or source systems such as ERP (e.g., SAP, Oracle), CRM (e.g., Salesforce, HubSpot), HRMS (e.g., Workday, SuccessFactors), or Marketing Platforms (e.g., Google Ads, LinkedIn).
These systems feed data into a central data warehouse like Snowflake, BigQuery, or Redshift  from which BI tools read and visualize information.

However, in real-world scenarios, business users often need to manually input or adjust small portions of data 

Example:

• 1. Entering budget targets or manual forecasts
• 2. Adding review comments or approval statuses
• 3. Maintaining mapping tables or data overrides

Traditionally, performing these updates requires technical support or direct database access, which business users typically lack. This leads to dependency on technical teams, manual data handling through Excel or Google Sheets and inefficiencies in updating or reusing this information across reports and dashboards.

As a result, organizations face challenges in maintaining data accuracy, timeliness and collaboration efficiency within their analytics ecosystem.

To Resolve this we have best approach using Sigma input tables, enabled through sigma write back features.

Sigma’s Solution

Sigma Computing bridges this gap with its Sigma Input Tables and Sigma Write-Back Tables features.These capabilities empower business users to enter, edit and persist data directly within Sigma, without leaving the BI environment.

Together, these features transform Sigma from a read-only BI platform into a bi-directional analytics environment, enabling users to both consume and contribute data.

To write data back to the warehouse, you first need to create an Input Table in Sigma and then convert it into a Write-Back Table.

Steps to Enable Write-Back from Sigma to the Database

i. Enable Write-Back in the Connection

• a. Open the Connection Settings in Sigma.
• b. Enable the Write-Back option.
• c. Enter the Project Name and Dataset (or Schema) where you want Sigma to store the write-back views.
• d. This setup allows Sigma to create and manage write-back tables or views directly in your specified warehouse location.

ii. Create Input Tables

After enabling Write-Back in the connection, you can start creating Sigma input tables.

Sigma provides three types of Input Tables:

Sigma provides three types of Input Tables:

• 1. Empty Input Table: A blank table within the workbook where users can manually enter values or create columns as needed. This is useful for capturing new or ad-hoc data directly in Sigma.
  

• 2. Linked Input Table: Connects an editable input layer to an existing dataset or visualization in Sigma.
  It allows users to add new columns or annotations to rows that already exist in a warehouse-backed dataset, without modifying the source data itself.The link is established through a unique key column, such as an ID or Name.
  

• 3. CSV Input Table: Created by uploading an external CSV file into Sigma.The uploaded file’s contents are automatically converted into a Sigma Input Table, preserving all rows and columns.Once imported, the table becomes fully editable, allowing users to add, edit, or remove data directly within Sigma.

  

After selecting the type of Input Table, choosing a connection is mandatory for all Input Tables.
The connection defines where Sigma will store the user-entered data and provides the security and governance context for that data.

Input Tables must be stored because they contain manual inputs that Sigma needs to preserve for future use, collaboration and analysis.

• a. If Write-Back is disabled, the data is stored in Sigma’s managed cloud storage (Sigma’s internal backend).
  
• b. If Write-Back is enabled, the data is stored in the connected data warehouse (e.g., Snowflake, BigQuery) under a Sigma-managed schema, fully aligned with sigma computing input tables best practices.

iii. Converting Input Tables to Write-Back Tables

Once you have created Input Tables (Empty, Linked, or CSV), you can enable Write-Back for each table by selecting Advanced Options → Create Warehouse View. This option allows you to define a custom view name as per your preference.

After selecting Create, Sigma will generate the view in the specified warehouse path. Make sure to publish the Input Table either before or after creating the view, or after enabling Write-Back, to ensure the warehouse is updated with the latest data changes.

 Example Use Case

For instance, a Finance Manager can enter next quarter’s forecast adjustments directly in Sigma.

Once submitted:

• 1. Sigma writes the entered data to a Snowflake write-back table (e.g., FIN_FORECAST_ADJUSTMENTS).
• 2. A warehouse view (e.g., VW_FORECAST_COMBINED) automatically merges the new forecast inputs with existing actuals.
• 3. Dashboards instantly reflect the latest forecasts without any engineering effort or manual updates.
• 4. The created warehouse view can be reused across multiple dashboards and reports, ensuring consistent and up-to-date insights.
• 5. Any future data additions or edits made in Sigma are written back to the database and automatically reflected wherever the view is used.

Conclusion

This write-back capability lets business users enter targets, forecasts, comments, and adjustments directly in Sigma without needing any database or technical knowledge. All the data they enter is properly managed, reusable, and stays consistent across dashboards, reports, and analytics workflows. It helps business and technical teams work together more easily and turns Sigma from a read-only tool into one where people can both view and add information in real time. This supports the idea of making data accessible to everyone, allowing users not only to see insights but also contribute to them.