Date format in conditional transition

What is the correct format to use for a date attribute when you are doing a conditional transition in Process Builder? I want to test whether a date has been entered or not. If I type in anything here, I get an error saying it is in the wrong format. If I leave it blank, I get an error when I try to run the process, giving an error on parsing the date. Any help would be appreciated.

Find more posts tagged with

Comments

DCTM_Guru

Are you trying to test for a date in any particular format? If so, I dont think is possible using OOTB feature. You can evaluate a date against another date or perform date addition or subtraction, but determining a value isDate() doesnt exist.

tcsimon58-E26LH

I'm not looking for a specific date, just whether or not the date field is null.

DCTM_Guru

Gotcha, so you are really asking how to enter a valid date. Did you define the attribute type as TIME? If not, this might be the problem. If so, the webtop UI should display a calendar control that will correctly "format" the date value.

tcsimon58-E26LH

The process variable, called duedate, is defined as a DATE. In the transition dialog, under the value field where it gives the hint, it says "date (MM/dd/yyyy <HH:mm:ss>)" so it knows it's a date. I tried useing nulldate and it validates but I still get an error when I run it in debug and if I just run it in TaskSpace (or DA) the workflow stops there. I don't see any errors in the log files.

DCTM_Guru

Sorry, I thought you were doing this as part of the data dictionary for an attribute, not through process builder. I dont recall how to do date comparison in PB.

tcsimon58-E26LH

You cannot test a date (or other format) against null in the Process builder transition condition. This has been confirmed with EMC engineering. What I have wound up doing is to set a default date and then have the condition test against the date. There are some quirks to this, however. When you type in the date in the condition, do not use any time (even though the default date that you set on the data tab for your process will show H:M:S). Also, I was trying to set a default date that would be early enough to not interfere with a "real" date for my customers. I started out trying 01/01/1900 and it failed. Dates that are too early will not come up as equal, even if they are. I am using 01/01/1940 as a comparison date. 01/01/1930 failed.

DCTM_Guru

Thanks for sharing what EMC has stated as well as your solution.