Data Collection#

Reportworq supports several functions (RW.ADAPTIVE.INPUT and RW.ADAPTIVE.MODELEDINPUT) that are used to "writeback" data into Workday (specifically Standard Sheets, Modeled Sheets, and Adaptive Cube Sheets). These formulas are only available and executed when Reportworq receives a file for processing using a Reportworq Data Collection license.

The functions described in this section are specific to Workday Adaptive Planning datasources.

RW.Adaptive.Extract#

RW.Adaptive.Extract aka AIExtract Generates an Adaptive report into a worksheet range by combining RW.Adaptive.Tier helper formulas with RW.Adaptive.Option settings. If you are on a version earlier than 5.0.0.91 please use AIExtract.

Syntax#

=RW.Adaptive.Extract(targetRange, tiersRange, optionsRange)

Arguments#

Behavior#

• RW.Adaptive.Extract gathers all RW.Adaptive.Tier formulas from tiersRange and splits them into rows, columns, and filters.
• At least one row tier and one column tier are required.
• RW.Adaptive.Option("AutoFormat", ...) controls whether ReportWorq bolds the row and column labels and auto-fits the label columns.
• The formula imports the Adaptive result set into targetRange and clears the formula cell on success.
• During Adaptive formula processing, modeled exports run first, then RW.Adaptive.Extract runs after the workbook's Adaptive specs have already been expanded.

Usage notes#

• RW.Adaptive.Extract is the main report-output formula for Adaptive custom reports.
• Keep your RW.Adaptive.Tier and RW.Adaptive.Option helper formulas in small setup ranges and pass those ranges into RW.Adaptive.Extract.
• Use RW.Adaptive.Option to control formatting and suppression instead of hard-coding those behaviors into the template.

Examples#

=RW.Adaptive.Extract(A1, TierSetup!A1:C10, OptionSetup!E1:E5)

=RW.Adaptive.Extract(B5, {Rows!A1:A5, Cols!C1:C3, Filters!E1:E2}, Options!G1:G3)

Common mistakes#

RW.Adaptive.Tier#

RW.Adpative.Tier aka AITier Defines one Adaptive tier for the row axis, column axis, or filter axis of an RW.Adaptive.Extract report. If you are on a version earlier than 5.0.0.91 please use AITier.

Syntax#

=RW.Adaptive.Tier(axis, dimensionName, selections, [expansionType], [order])

Arguments#

Behavior#

• RW.Adaptive.Tier resolves the dimension by name in Adaptive metadata.
• With expansionType="none", at least one element must be supplied.
• With children, descendants, or leaf, the implementation can expand from the supplied members or from the dimension root when no members are supplied.
• RW.Adaptive.Extract sorts row and column tiers by order before building the request.

Usage notes#

• Put outer tiers at lower order values and inner tiers at higher values.
• Use leaf when you want fully expanded leaf-level members rather than parent members.
• Use filters for dimensions that should filter the report but should not appear as row or column labels.

Examples#

=RW.Adaptive.Tier("rows", "Period", A1:A5)

=RW.Adaptive.Tier("columns", "Region", B1:B2, "children", 1)

=RW.Adaptive.Tier("filters", "Version", "Actual;Budget")

Common mistakes#

RW.Adaptive.Option#

RW.Adaptive.Option aka AIOption Defines an option that RW.Adaptive.Extract reads when building an Adaptive report. If you are on a version earlier than 5.0.0.91 please use AIOption.

Syntax#

=RW.Adaptive.Option(optionName, optionValue)

Arguments#

Behavior#

• ReportWorq stores the option as text and also tries to parse it as a boolean and as an integer.
• RW.Adaptive.Extract looks up options by name when it decides how to build and format the report.
• The formula cell displays optionName=optionValue.

Usage notes#

• Use AutoFormat to control whether RW.Adaptive.Extract bolds labels and auto-fits label columns.
• Use SuppressRollups and SuppressZeros to control the Adaptive request rather than post-processing the result in Excel.

Examples#

=RW.Adaptive.Option("AutoFormat", TRUE)

=RW.Adaptive.Option("SuppressZeros", 2)

=RW.Adaptive.Option("SuppressRollups", FALSE)

Common mistakes#

• Misspelling the option name; unknown names are simply not used by the consuming formula.
• Expecting numeric options to work when the value is text that cannot be parsed as an integer.

RW.Adaptive.Filter#

RW.Adpative.Filter aka AIFilter Stores a reusable Adaptive dimension filter made up of a dimension name and one or more member names. If you are on a version earlier than 5.0.0.91 please use AIFilter.

Syntax#

=RW.Adaptive.Filter(dimensionName, memberNames)

Arguments#

Behavior#

• ReportWorq stores the dimension name and the resolved member list.
• Literal lists and cell-based lists are both supported.
• The formula cell displays a simple dimension.members summary string.

Usage notes#

• Use RW.Adaptive.Filter when you want a compact filter definition that can be referenced elsewhere in an Adaptive template.
• For full row/column/filter layout in an Adaptive report, use RW.Adaptive.Tier and RW.Adaptive.Extract.

Examples#

=RW.Adaptive.Filter("Region", A1:A5)

=RW.Adaptive.Filter("Version", {"Actual","Plan"})

Common mistakes#

• Supplying a dimension name that does not exist in Adaptive metadata.
• Expecting RW.Adaptive.Filter by itself to render a report grid; it only defines filter values.

RW.Adaptive.ModeledExport#

RW.Adaptive.ModeledExport aka AIModeledExport exports modeled Adaptive data into a worksheet range or named table.If you are on a version earlier than 5.0.0.91 please use AIModeledExport.

Syntax#

=RW.Adaptive.ModeledExport(targetRange, version, [adaptiveSheetName], [startPeriod], [endPeriod], [levels], [includeDescendent], [isGlobal])

Arguments#

Behavior#

• ReportWorq can write the export into a normal range or into a named Excel table.
• When levels is supplied, it is split on | before the export request is sent.
• If the export returns rows, the data is imported and the formula cell is cleared.
• Modeled exports run before RW.Adaptive.Extract during the Adaptive formula pass.

Usage notes#

• Use RW.Adaptive.ModeledExport when you want modeled-sheet data rather than a custom RW.Adaptive.Extract layout.
• Exporting into a table is useful when downstream formulas, filters, or charts should grow with the result set.

Examples#

=RW.Adaptive.ModeledExport(A1, "ActualData")

=RW.Adaptive.ModeledExport(SalesTable, "PlanModel", "CommissionSheet", "2026-01", "2026-12")

=RW.Adaptive.ModeledExport(B5, "ForecastData", , , , "Level1|Level2", TRUE, FALSE)

Common mistakes#

• Supplying an invalid target range or table name.
• Expecting levels to use commas; the implementation splits on |.
• Forgetting that blank optional arguments still need placeholder commas if a later argument is used.

RW.Adaptive.Input#

RW.Adpative.Input aka AIInput marks a cell as an Adaptive input and prepares it for upload during contribution processing.If you are on a version earlier than 5.0.0.91 please use AIInput.

Syntax#

=RW.Adaptive.Input(inputCell, [adaptiveSheetName], [tuplePart1], [tuplePart2], ...)

Each optional tuplePart is a text value in the form Dimension|Member.

Arguments#

Behavior#

• With no adaptiveSheetName, the formula uploads to a standard account target.
• With a non-blank adaptiveSheetName, the formula uploads to a cube account target.
• If tuple parts are not supplied in the formula, ReportWorq looks up the tuple from workbook metadata that was prepared during report generation.
• The formula is processed during input submission, not during the report-output pass.

Usage notes#

• Use explicit tuple parts when you want the workbook formula itself to define where the value is written.
• Leave tuple parts out when the generated workbook already contains the tuple map that ReportWorq created for the input cell.
• On success, the formula cell is cleared.

Examples#

=RW.Adaptive.Input(B5)

=RW.Adaptive.Input(B5, "CommissionSheet")

=RW.Adaptive.Input(B5, "CommissionSheet", "Version|Plan", "Period|2026-01", "Region|East")

Common mistakes#

RW.Adaptive.ModeledInput#

RW.Adpative.ModeledInput aka AIModeledInput updates a modeled Adaptive sheet by matching one key value and writing one modeled field value. If you are on a version earlier than 5.0.0.91 please use AIModeledInput.

Syntax#

=RW.Adaptive.ModeledInput(version, adaptiveSheetName, importKeyName, importKeyValue, inputValueName, inputValue)

Arguments#

Behavior#

• All six parameters are required.
• The formula builds a small two-column modeled-data update request and sends it during input processing.
• On success, the formula cell is cleared.
• The implementation comment specifically notes that INDIRECT(...) can be helpful when formulas are copied to repeated worksheet rows.

Usage notes#

• Use RW.Adaptive.ModeledInput for modeled-sheet row updates.
• Use RW.ADAPTIVE.INPUT instead for standard or cube-account uploads that rely on tuple metadata.

Examples#

=RW.Adaptive.ModeledInput($C$2, "CommissionSheet", "Employee_ID", A2, "Target_Commission", B2)

=RW.Adaptive.ModeledInput("2026_Plan", "Targets", "Region", INDIRECT("A" & ROW()), "Headcount", INDIRECT("B" & ROW()))

Common mistakes#