Is your field an actual Date/Time field type or a text field?
The target field is a date/time field, but I am open to options on a text field as well.
Is it always off by 49 hours?
Are you able to duplicate the issue using an Update Object Quick Action?
I'm on version 2016.1 and your expression works just fine both as an editing rule and a calculation rule. It also works as a quick action for both Date/Time fields and text fields. There may have been some tweaking between 2014.3 and 2016.1 on date and time fields and calculations. Have you spoken with HEAT Software Support?
How in the heck are you getting this to work?!?
I am on 2017.2 and I am not having any luck. :-(
I entered your expression above a pressed Simplify Expression it is converted to:
$(DateTime(FormatDate(DateTime(ML_DueDate + " " + ML_DueTime), "mm/dd/yyyy hh:mm")))
Now when I use the form and select a date or time the following error pops up.
The end goal is to be able to use this DueDate with the TargetDate to determine correct escalation dates/times. Also to sort dashboards and lists based on Due/Target priorities.
Hoping one of you brilliant people can come to my rescue! Thanks - Mark.
The answer to this is to use a Before Save Rule to add the two fields together.
Edit Rules and Calculation Rules DO NOT work.
Before Save Rule $(DateTime(FormatDate(DateTime(ToString(ML_DueDate)), "MM/dd/yyyy") + " " + FormatDate(ML_DueTime, "hh:mm tt")))
ML_DueDate: Type Binding - Date
ML_DueTime: Type Binding - Time
ML_DueDateTime: Type Binding - Date & Time
So thrilled as I have been trying to figure this out for a long time.
Thank you to those who have posted!!! Hope to meet you in Texas in May. Mark
And I too, have found that the date and time were off by a day and some hours. I assume this has to do with data entry vs UTC time and the timze zone set on our servers.
Here is what finally worked: (Note the AddDays and the Timezone additional)
$(DateTime(FormatDate(DateTime(ToString(AddDays(1, DueDate))), "MM/dd/yyyy") + " " + FormatDate(DueTime, "hh:mm tt", "America/Chicago")))
I just tested this using a computer set to another timezone and the day and time are incorrect. Back to the drawing board! I'll post when I have it sorted out.
That's what I get for thinking I had it solved at home and not doing my due diligence in testing. :-(