LOOKUP: from Tableau to SQL

Returns the previous addressed mark revenue, or null outside the partition. Below, 8 sample rows go through the calculation and through the SQL, and both return the same numbers.

Calculated field

LOOKUP(SUM([Revenue]), -1)

Compute using: addressing Period; partitioning Region

Sample data

RegionPeriodRevenueCost
Harbor112070
Harbor2180100
Harbor3180120
Harbor4240140
Upland19050
Upland2150110
Upland3null90
Upland4330190

The same calculation as SQL

SELECT CAST((lag("Revenue",1) OVER (PARTITION BY "Region" ORDER BY "Period")) AS DOUBLE) AS result FROM input ORDER BY "Region", "Period"

Runs the example above.

Result

RegionPeriodRevenueCostresult
Harbor112070null
Harbor2180100120
Harbor3180120180
Harbor4240140180
Upland19050null
Upland215011090
Upland3null90150
Upland4330190null

Same rows from the calculation and from the SQL in DuckDB.

Where a naive translation goes wrong

  • Omitting the region partition allows a calculation to consume marks from other regions.

    Naive SQL

    SELECT CAST((lag("Revenue",1) OVER ( ORDER BY "Period")) AS DOUBLE) AS result FROM input ORDER BY "Region", "Period"
    RegionPeriodRevenueCostresult
    Harbor112070null
    Harbor218010090
    Harbor3180120150
    Harbor4240140null
    Upland19050120
    Upland2150110180
    Upland3null90180
    Upland4330190240

    Matches the calculation

    SELECT CAST((lag("Revenue",1) OVER (PARTITION BY "Region" ORDER BY "Period")) AS DOUBLE) AS result FROM input ORDER BY "Region", "Period"
    RegionPeriodRevenueCostresult
    Harbor112070null
    Harbor2180100120
    Harbor3180120180
    Harbor4240140180
    Upland19050null
    Upland215011090
    Upland3null90150
    Upland4330190null

Signature

LOOKUP(expression, offset?)