Qlik Replicate’s transformation engine is SQLite-based; therefore any computed column can use SQLite date/time functions.

The SQLite/Replicate function

strftime('%s', )

returns “the number of seconds since 1970-01-01 00:00:00 UTC”, i.e., Unix epoch time.

Option D uses exactly that call against the source column SARHCOMMITTIMESTAMP; the second term strftime('%s','1970-01-01 00:00:00') evaluates to 0, so the subtraction leaves the epoch value unchanged. Hence D correctly converts the stored timestamp to Unix time.

A. Uses incorrect datetime syntax and compares values; does not call strftime nor return epoch seconds.

B. datetime(,'localtime','unixepoch') converts FROM epoch TO human time, the opposite direction.

C. Mixes SQLite strftime with Python datetime; invalid in Replicate expression engine.

E. Ruby-style Time.now … not recognized by Qlik Replicate/SQLite expressions.

1. Qlik Replicate and Compose – “Functions and Expressions Guide”, May 2023, Section “Date/Time Functions”, p. 37: “strftime('%s', timestring) → seconds since 1970-01-01”.

2. Qlik Replicate Help (August 2023) – Topic “Using SQLite functions in transformations”, example 3 “Convert timestamp to Unix epoch with strftime('%s', column)”.

3. SQLite Documentation, langdatefunc.html, paragraph “strftime”: “%s … returns seconds since 1970-01-01 00:00:00 UTC” (retrieved 2025-11-26).