stalbert
01/29/2019, 12:30 AMPeter Bertelsen
01/29/2019, 6:48 AMPeter Bertelsen
01/29/2019, 12:05 PMmg2017
01/29/2019, 3:19 PMZaanton
01/29/2019, 3:36 PMmattdahse
01/29/2019, 3:37 PMZaanton
01/29/2019, 3:37 PMZaanton
01/29/2019, 3:38 PMmattdahse
01/29/2019, 3:42 PMerictgrubaugh
01/29/2019, 3:51 PMitem
is not a valid Search Column on an MOT according to the Records Browserganoo7
01/29/2019, 4:09 PMerictgrubaugh
01/29/2019, 4:13 PMDate
Objects? Or just Strings?erictgrubaugh
01/29/2019, 4:15 PMDates
that way, but be aware that you can't determine whether two Dates
are the same with ===
or ==
erictgrubaugh
01/29/2019, 4:19 PMmoment.js
plug:
var a = moment("1/29/2019", "M/d/YYYY");
var b = moment("2/3/2019", "M/d/YYYY");
a.isBefore(b); // => true
erictgrubaugh
01/29/2019, 4:20 PMganoo7
01/29/2019, 4:21 PMerictgrubaugh
01/29/2019, 4:24 PMdate1 < date2
), try the getTime()
method, which returns the UNIX timestamp in ms (date1.getTime() < date2.getTime()
)jarens
01/29/2019, 4:54 PMjeffmillies
01/29/2019, 4:54 PMcontext.newRecord.setValue(field, value);
I had logging setup to make sure the value was correct, but doesn't seem to stick when looking at the record after it is submittedjeffmillies
01/29/2019, 4:55 PMjeffmillies
01/29/2019, 5:00 PMerictgrubaugh
01/29/2019, 5:05 PMsetValue()
should be all you need in beforeSubmit
jeffmillies
01/29/2019, 5:07 PMjeffmillies
01/29/2019, 5:07 PMerictgrubaugh
01/29/2019, 5:08 PMafterSubmit
sometimesjeffmillies
01/29/2019, 5:08 PMprachi
01/29/2019, 5:38 PMerictgrubaugh
01/29/2019, 5:47 PMcreatedfrom
fieldprachi
01/29/2019, 5:53 PMapaule
01/29/2019, 6:19 PM