Skip to main content
Example Transformer: Common Date Formats Reference walkthrough of the Common date formats example configuration: relative date calculations and standard date/time output formats for transformer chains.

​
Overview

This page documents an importable Data Integrator example configuration (register.configuration.json) named [Example] — Common date formats (identifier example-common-date-formats). It is not built to solve one specific integration; it is a reference snippet consultants can copy into a real flow and adapt.
The configuration is a plain list-transformer object, so it can be imported directly into a Data Integrator environment and inspected transformer-by-transformer in the flow builder.
The example is a single data transformer with two value-setter blocks: one that evaluates relative date expressions, and one that reformats the current moment into several standard formats.
The relative expressions (yesterday, next monday, first day of this month, …) and the toFormat tokens (Y, m, d, H, i, s, c, r, U, W, P) follow PHP’s strtotime() phrasing and date() format characters, which is the convention the format-date mapper is built on.

​
Relative date expressions

Example outputs below assume a flow running on Monday, 7 September 2026, 14:32 (Europe/Amsterdam, UTC+2).
yesterday and tomorrow reset the time portion to 00:00:00, while +7 days / -30 days preserve the original time of day. next monday, evaluated from a Monday, jumps a full week ahead rather than staying on the same day, this is standard strtotime() behavior and easy to trip over when a flow runs on a Monday.
The block also contains a today_with_timezone entry with toFormat set to Y-m-d\TH:i:sP\ (note the trailing backslash). That trailing backslash is a harmless leftover, PHP-style date formatting ignores a dangling escape, so the output is identical to the ISO-8601 c format shown below: 2026-09-07T14:32:00+02:00. If reusing this pattern, drop the trailing backslash (Y-m-d\TH:i:sP) for clarity.

​
Well-known date/time formats

The second block formats “now” (an empty input value) into several standard representations:
ISO_8601_in_UTC appends a literal Z, it does not convert the value to UTC first. Use it only when the underlying date is already in UTC. When the value is in a local timezone (as in this example, Europe/Amsterdam), prefer ISO_8601_with_timezone (c), which encodes the real offset instead of a false Z.

​
Format token quick reference

​
Transformer prototypes used

The example is self-contained enough to import as-is, run once, and inspect the output per field, which is the fastest way to confirm a date format behaves the way a ticket or requirement expects before wiring it into a production flow.