Skip to content

Date Time Functions

Fuuz Wiki Import edited this page Jun 7, 2026 · 2 revisions

Date/Time Functions

Date/time utilities are commonly used in Fuuz to timestamp transactions, align timezones across plants, and format values for downstream systems (e.g. SAP, Oracle, or machine HMIs). All functions execute with a single evaluation timestamp per message.

Fuuz Context

  • Timezones: Use the picture/offset parameters of $fromMillis() when normalizing to plant-local time (e.g. "-0500" for US Eastern).
  • Idempotency: Capture $millis() into a key to de-duplicate replays across the Fuuz data platform.
  • Formatting: When integrating with legacy systems, use picture strings to emit RFC-compatible timestamps expected by those systems.

$now()

Signature: $now([picture [, timezone]])

Generates a UTC timestamp in ISO 8601 compatible format and returns it as a string. All invocations of $now() within an evaluation of an expression will return the same timestamp value.

If the optional picture and timezone parameters are supplied, then the current timestamp is formatted as described by the $fromMillis() function.

Examples

  • $now() => "2017-05-15T15:12:59.152Z"

$millis()

Signature: $millis()

Returns the number of milliseconds since the Unix Epoch (1 January 1970 UTC) as a number. All invocations of $millis() within an evaluation of an expression will return the same value.

Examples

  • $millis() => 1502700297574

$fromMillis()

Signature: $fromMillis(number [, picture [, timezone]])

Convert the number representing milliseconds since the Unix Epoch (1 January 1970 UTC) to a formatted string representation of the timestamp as specified by the picture string.

If the optional picture parameter is omitted, then the timestamp is formatted in the ISO 8601 format.

If the optional picture string is supplied, then the timestamp is formatted according to the representation specified in that string. The behaviour of this function is consistent with the two-argument version of the XPath/XQuery function fn:format-dateTime as defined in the XPath F&O 3.1 specification. The picture string parameter defines how the timestamp is formatted and has the same syntax as fn:format-dateTime.

If the optional timezone string is supplied, then the formatted timestamp will be in that timezone. The timezone string should be in the format ±HHMM, where ± is either the plus or minus sign and HHMM is the offset in hours and minutes from UTC. Use a positive offset for timezones east of UTC, and a negative offset for timezones west of UTC.

Examples

  • $fromMillis(1510067557121) => "2017-11-07T15:12:37.121Z"
  • $fromMillis(1510067557121, '[M01]/[D01]/[Y0001] [h#1]:[m01][P]') => "11/07/2017 3:12pm"
  • $fromMillis(1510067557121, '[H01]:[m01]:[s01] [z]', '-0500') => "10:12:37 GMT-05:00"

$toMillis()

Signature: $toMillis(timestamp [, picture])

Convert a timestamp string to the number of milliseconds since the Unix Epoch (1 January 1970 UTC) as a number.

If the optional picture string is not specified, then the format of the timestamp is assumed to be ISO 8601. An error is thrown if the string is not in the correct format.

If the picture string is specified, then the format is assumed to be described by this picture string using the same syntax as the XPath/XQuery function fn:format-dateTime, defined in the XPath F&O 3.1 specification.

Examples

  • $toMillis("2017-11-07T15:07:54.972Z") => 1510067274972

See Also


Source: support.fuuz.com

🏠 Home

Getting Started (14)
Training Guides (52)

Applications

Access & Users

Data Models & Schema

Screens

Weather Lookup Series — guided 3-part build

Data Flows & Integrations

Data, Reporting & Monitoring

Enterprise & Organizations

Platform Concepts & Architecture (10)
Screens & Application Design (17)
Data Models & Schema (8)
Data Flows & Scripting (51)

Designing Flows

Data Flow Nodes

JSONata Reference

Scripting

Integrations & Connectors (30)

General & iPaaS

Plex

EDI

IIoT & Edge Gateway (18)

Physical Device Connectors

Edge Data Connectors

Reporting, Documents & Dashboards (8)
Administration & Access Control (27)
Data Management (8)
Accelerators, Templates & Packages (8)
Design Standards (1)
How-To Guides (8)
FAQ & Troubleshooting (1)
Release Notes (117)

2026

2025

2024

2023

2022

2021

2020

Policies & Company (6)

Clone this wiki locally