In our app, we have a schedule domain where we centralize most of our date time and calendar functions. For appointments, the start and end dates were localized. When calculating hours between, or start times using [%EndOfCurrentDay%] as a reference point, the results indicated that the system was shifting the date time value of the attribute based on localization. In other words, if the value of the date time attribute was 10/3/2014 5:00PM, since we are in UTC-5 (Eastern US/Canada), when the calculation was made, the result was as if the value of the attribute was 10/3/2014 10:00PM. I've turned off localization and am testing now. Any input is appreciated. Thanks