RE: Custom Field Date time issues

joseg199 — Fri, 13 Oct 2023 16:20:25 GMT

Thank you Mike for the updates. we have fixed the issue by adding a local time zone function a!match(
value: rv!record['recordType!{942022df-8dbc-4911-b991-b4a48224c936}MECMS Case.fields.{213813ef-766f-4d3d-95c4-3d6963ed19bd}createdOn'],
whenTrue:and(
    hour(local(fv!value)) >= 7,
    hour(local(fv!value)) < 15
),
then: "Shift 1",
whenTrue: and(
    hour(local(fv!value)) >= 15,
    hour(local(fv!value)) < 23
),
then: "Shift 2",
default: "Shift 3",
)

RE: Custom Field Date time issues

Mike Schmitt — Fri, 13 Oct 2023 16:01:06 GMT

Have you tried explicitly handling NULL values in your a!match() statement? hour() breaks if passed null. Just my first guess.

If so, the fix is pretty easy: