日期函数 date-functions

currentTimeInMillis()

返回整数。

currentTimeInMillis()

返回“1544712617131”。

两个参数必须使用相同的数据类型；不支持混合类型（例如，dateOnly与dateTime）。 参数可以是文本日期值、其他函数（如now()）或上下文属性（事件有效负载字段、自定义操作响应字段、配置文件或实体字段以及变量），只要它们被键入为dateOnly、dateTimeOnly或dateTime。

dateDiff(<dateOnly>,<dateOnly>)

返回一个整数，表示两个日期之间的天数。

dateDiff(<dateTimeOnly>,<dateTimeOnly>)

返回一个整数，表示两个日期时间之间的毫秒数。

dateDiff(<dateTime>,<dateTime>)

返回一个整数，表示两个日期时间之间的毫秒数。

dateDiff(toDateOnly('2023-12-15'), toDateOnly('2023-12-12'))

返回3（天）。

dateDiff(toDateTimeOnly('2023-12-15T00:00:00'), toDateTimeOnly('2023-12-12T00:00:00'))

返回259200000（毫秒，相当于3天）。

dateDiff(now(), toDateTime('2024-12-25T00:00:00Z'))

返回从今天到2024年12月25日之间的毫秒数。

dateDiff(#{ExperiencePlatform.ProfileFieldGroup.person.birthDate}, toDateOnly('2023-01-01'))

返回用户档案的birthDate字段与2023年1月1日之间的天数，假定将birthDate键入为dateOnly。

inLastDays(<dateTime>,<integer>)

返回布尔值。

inLastDays(toDateTime('2023-12-12T01:11:00Z'), 4)

返回真。

inLastHours(<dateTime>,<integer>)

返回布尔值。

inLastHours(toDateTime('2023-12-12T01:11:00Z'), 4)

返回真。

inLastHours(@event{MyEvent.timestamp}, 4)

返回真。

inLastMonths(<dateTime>,<integer>)

返回布尔值。

inLastMonths(toDateTime('2023-12-12T01:11:00Z'), 4)

返回真。

inLastYears(<dateTime>,<integer>)

返回布尔值。

inLastYears(toDateTime('2023-12-12T01:11:00Z'), 4)

返回真。

inNextDays(<dateTime>,<integer>)

返回布尔值。

inNextDays(toDateTime('2023-12-12T01:11:00Z'), 4)

返回真。

inNextHours(<dateTime>,<integer>)

返回布尔值。

inNextHours(toDateTime('2023-12-12T01:11:00Z'), 4)

返回真。

inNextMonths(<dateTime>,<integer>)

返回布尔值。

inNextMonths(toDateTime('2023-01-12T01:11:00Z'), 4)

返回真。

inNextYears(<dateTime>,<integer>)

返回布尔值。

inNextYears(toDateTime('2021-12-12T01:11:00Z'), 4)

返回真。

now()

now("<timeZone id>")

返回日期时间。

now()

返回2023-06-03T06:30Z。

toString(now())

返回“2023-06-03T06:30Z”

now("Europe/Paris")

返回2023-06-03T08:30+02:00。

nowWithDelta(<delta>,<date part>

nowWithDelta(<delta>,<date part>,"<timeZone id>")

返回日期时间。

nowWithDelta(-2, "hours")

nowWithDelta(-2, "hours", "Europe/Paris")

返回2小时前的dateTime。

nowWithDelta(1, "months", "Asia/Tokyo")

在2026-01-31上进行评估时，返回2026-02-28T…；在2026-05-31上进行评估时，返回2026-06-30T…

nowWithDelta()使用日历月算术。 如果目标月份的日期少于当前月份的日期，则将结果规范化为该月的最后一个有效日期。 该函数不会滚动到下一月。

setHours(<dateTime>,<hours>)

返回日期时间。

setHours(<dateTimeOnly>,<hours>)

返回不考虑时区的日期时间。

setHours(toDateTime('2023-12-12T01:11:00Z'), 4)

返回2023-12-12T04:11:00Z。

setHours(nowWithDelta(1, "days"), 20)

返回明天晚上8:XY，XY是当前时间评估时刻的分钟数。 如果评估在凌晨2:45进行，则返回时间将为晚上8:45。

setDays(<dateTime>,<days>)

返回日期时间。

setDays(<dateTimeOnly>,<days>)

返回不考虑时区的日期时间。

setDays(toDateTime('2023-12-12T01:11:00Z'), 25)

返回2023-12-25T01:11:00Z。

setDays(toDateTimeOnly(@event{MyEvent.registrationDate}), 1)

• 时区id：字符串
• dateTime

updateTimeZone(<dateTime>,<timeZone id>)

返回日期时间。

updateTimeZone( toDateTime("2023-08-28T08:15:30.123-07:00"), "Europe/Paris"))

返回2023-08-28T17:15:30.123+02:00。

updateTimeZone(@event{MyExpEvent.timestamp}, "Australia/Sydney")

如果时间戳字段的值为2021-11-16T16:55:12.939318+01:00，则函数返回2021-11-17T02:55:12.942115+11:00。

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

• TL;DR: This page documents all date and time functions available in AJO journey expressions, covering how to get the current time, check whether a date falls within a relative time window, and modify date/time components.

Intents:

• Get the current datetime (with optional timezone) using now or nowWithDelta
• Retrieve the current time as an epoch integer using currentTimeInMillis
• Calculate the difference between two dates or date-times using dateDiff
• Check if a datetime falls within the last N days, hours, months, or years using inLastDays, inLastHours, inLastMonths, inLastYears
• Check if a datetime falls within the next N days, hours, months, or years using inNextDays, inNextHours, inNextMonths, inNextYears
• Force a specific hour or day of the month on a datetime value using setHours or setDays
• Convert a datetime to a different timezone while preserving the same instant using updateTimeZone

Glossary:

• dateOnly: A date value with no time or timezone information (product-specific)
• dateTime: A date-time value that includes timezone offset information (product-specific)
• dateTimeOnly: A date-time value with no timezone information (product-specific)
• epoch milliseconds: An integer representing the number of milliseconds elapsed since 1970-01-01T00:00:00Z
• delta: An integer offset (positive or negative) used with nowWithDelta to shift the current time by a number of years, months, days, hours, minutes, or seconds

Guardrails:

• now() is only available in journey expressions; for email personalization use getCurrentZonedDateTime() instead
• The timezone ID in nowWithDelta must be a string constant — field references and dynamic expressions are not supported
• The timezone ID in updateTimeZone must be a string constant
• dateDiff requires both parameters to be the same data type (dateOnly, dateTimeOnly, or dateTime); mixing types is not supported
• dateDiff returns null if either parameter is null
• dateDiff returns days for dateOnly parameters, but milliseconds (not days) for dateTimeOnly and dateTime parameters — convert accordingly when comparing results across types

Terminology:

• Canonical name: Date functions — Acronym: none — variants: date-time functions, temporal functions
• Synonyms: “now()” = “current datetime”; “currentTimeInMillis()” = “current epoch milliseconds”
• Do not confuse: “inLastDays” (looks back in time) ≠ “inNextDays” (looks forward in time)
• Do not confuse: “setHours” (replaces the hour component) ≠ “nowWithDelta” (offsets the current time)
• Do not confuse: “updateTimeZone” (same instant, different timezone representation) ≠ “setHours” (changes the time value itself)
• Do not confuse: the journey expression editor’s dateDiff (accepts dateOnly, dateTimeOnly, or dateTime; returns days or milliseconds depending on type) ≠ the personalization editor’s dateDiff (accepts only dateTime; always returns days)

FAQ:

• Q: Can I use now() in email personalization content? — No, now() is only available in journey expressions. Use getCurrentZonedDateTime() for email personalization.
• Q: How do I check if an event happened in the last 24 hours? — Use inLastHours(@event{MyEvent.timestamp}, 24).
• Q: How do I get the current time offset by 2 hours in the past? — Use nowWithDelta(-2, "hours").
• Q: What does updateTimeZone do differently from setHours? — updateTimeZone keeps the same instant in time but expresses it in a different timezone, while setHours actually changes the hour component of the datetime value.
• Q: Can the timezone parameter in nowWithDelta be a profile field? — No, the timezone ID must be a string constant; field references are not supported.
• Q: What happens when nowWithDelta() is used with months and the current date is a month-end date? — The function uses calendar-month arithmetic and normalizes the result to the last valid day of the target month. For example, adding 1 month to January 31 returns February 28 (not March 3).