On a system where both server and client have the same Regional Settings applied which display a DateTime as 'dd-MM-yyyy HH:mm:ss' (eg 10-02-2023 11:17:00), we see some strange behaviour when generating dynamic booking shapes which include the start and end time of the booking.

More specifically, we see that a few shapes put the day before the month (which is expected) while most of the other shapes do the opposite, even though they use identical shape data. Please see the highlighted parts in the image below:

Follwing shape data is used within the booking grouped shape:

For the start time:

[Sum:[Subtract:[LocalTime],[UTCTime]],[Start]]

For the end time:

[Sum:[Subtract:[LocalTime],[UTCTime]],[End]]

I already tried to force the format using the '|Format=dd-MM-yyyy HH:mm:ss', but that doesn't seem to work.

Note that the 'Start' and 'End' custom booking properties which are referenced in the shape data, are stored like this:

So, there seem to be a lot of variables at play, but perhaps someone can shed some light, or come up with a solution?

Thanks!