Data Collection#

Reportworq supports several functions that are used to "writeback" data into configured SQL data sources. These formulas are only available and executed when Reportworq receives a file for processing using a Reportworq Data Collection license.

SQL Datasources (SQL Server, ODBC or OleDB)#

The functions described in this section are specific to SQL datasources (SQL Server, ODBC or OleDB).

RW.Relational.Export#

RW.Relational.Export aka RWSQL executes a SQL query and imports the result set into an Excel range or named table. If you are on version 5.0.0.91 or earlier use RWSQL.

Syntax#

=RW.Relational.Export(targetRange, connectionName, query)

Arguments#

Behavior#

• RW.Relational.Export runs as a one-time report-generation formula.
• If targetRange resolves to a named table, ReportWorq imports the data into the table body.
• Otherwise, ReportWorq writes the result set starting at the supplied range.
• The formula cell is set to the query text after a successful import.
• RW.Relational.Export runs before post-processing steps such as RW.Tools.Sort, RW.Tools.BlankRow, and RW.Tools.Suppress

Usage notes#

• Use a table target when you want Excel tables, structured references, or automatically expanding downstream charts.
• Leave enough room for the full query result when using a plain range target.

Examples#

=RW.Relational.Export(A1, "DefaultConnection", "SELECT * FROM Sales WHERE Year = 2026")

=RW.Relational.Export(SalesTable, "WarehouseDB", "SELECT CustomerID, Amount FROM Orders")

Common mistakes#

RW.Relational.Update#

RW.Relational.Update aka RWSQLUpdate writes values back to SQL by updating the row that matches a key column and key value. If you are on version 5.0.0.91 or earlier please use RWSQLUpdate.

Syntax#

=RW.Relational.Update(connectionName, table, idColumnName, idColumnValue, columnName1, value1, [columnName2, value2], ...)

Arguments#

Behavior#

• At least six arguments are required so that one column/value pair is present.
• The formula is processed during input/writeback handling.
• On success, the formula cell is cleared.
• ReportWorq records tuple-log information for the connection, table, key, and updated columns.
• Unlike RW.Relational.Upsert, RW.Relational.Update does not request insert behavior for missing keys.

Usage notes#

• Use RW.Relational.Update when the target row must already exist.
• Additional column/value pairs can be appended in the same formula.

Examples#

=RW.Relational.Update("DefaultConnection", "Users", "UserID", 123, "Email", "new@email.com")

=RW.Relational.Update("CRM", "Accounts", "AccountID", A1, "Manager", B2, "Territory", C3, "Priority", "High")

Common mistakes#

RW.Relational.Upsert#

RW.Relational.Upsert aka RWSQLUpsert writes values back to SQL by updating an existing row or inserting a new row when the key does not already exist. If you are on version 5.0.0.91 or earlier please use RWSQLUpdate.

Syntax#

=RW.Relational.Upsert(connectionName, table, idColumnName, idColumnValue, columnName1, value1, [columnName2, value2], ...)

Arguments#

Behavior#

• RW.Relational.Upsert shares the same parser and argument rules as RW.Relational.Update.
• During processing, ReportWorq enables the formula's upsert mode because the function name is RW.Relational.Upsert.
• On success, the formula cell is cleared.
• Tuple logging is captured in the same way as RW.Relational.Update.

Usage notes#

• Use RW.Relational.Upsert when the workbook may create brand-new rows as part of contribution processing.
• If the key already exists, the row is updated instead of inserted.

Examples#

=RW.Relational.Upsert("AnalyticsDB", "Forecasts", "ForecastID", "Q3_2026", "Revenue", 5000000, "Confidence", 0.95)

=RW.Relational.Upsert("CRM", "Accounts", "AccountID", A1, "Status", "Active", "Territory", B2)

Common mistakes#

• Expecting RW.Relational.Upsert to preserve unmatched trailing arguments; trailing odd arguments are ignored just as they are in RW.Relational.Update.
• Using it when inserts are not allowed by the target database or connection.