Anyone else hit an issue where the end user's date format is impacting a scripted search that is using a date? I tried this, and it works fine for me, but not another end user who the script is running for later:

var startDate=format.parse({value:"2020-01-01T12:00:00Z",type:format.Type.DATETIME})

var noteSearchObj=search.create({ type: "note", filters:[ [ ["customer.internalid","anyof",custNSID], "AND", ["notedate","onorafter",startDate] ] ],

standard advice: use Date's or N/format

Let me try format instead.

wont help

Ahh. Any ideas? I have not run into this before.

"2020-01-01T120000Z" is almost in ISO 8601 format

Yeah, my format is 2020-01-01 120000... But their format is that weird mm/dd/yy 12:00 format.

the Date constructor can create Date's from ISO-8601 format so use

var startDate = new Date("2020-01-01T12:00:00.000Z")

k, I'll try it.

full error message?

here's the latest one while messing around. Essentially the same error, about the format. {"type":"error.SuiteScriptError","name":"INVALID_DATE_VALUE_1_MUST_MATCH_2","message":"Invalid date value 2020-01-01T120000.000Z (must match yy-MM-dd h:mm a)","stack":["createError(N/error)","queryLatestUserNote(/SuiteScripts/O2_SuiteScripts/O2_UE_Customer_Update_Last_User_Note.js:99)","beforeSubmit(/SuiteScripts/O2_SuiteScripts/O2_UE_Customer_Update_Last_User_Note.js:38)"],"cause":{"type":"internal error","code":"INVALID_DATE_VALUE_1_MUST_MATCH_2","details":"Invalid date value 2020-01-01T120000.000Z (must match yy-MM-dd h:mm a)","userEvent":"beforesubmit","stackTrace":["createError(N/error)","queryLatestUserNote(/SuiteScripts/O2_SuiteScripts/O2_UE_Customer_Update_Last_User_Note.js:99)","beforeSubmit(/SuiteScripts/O2_SuiteScripts/O2_UE_Customer_Update_Last_User_Note.js:38)"],"notifyOff":false},"id":"","notifyOff":false,"userFacing":false}

that doesnt look like you put in a Date

The date is in the error: Invalid date value 2020-01-01T120000.000Z That was trying with the idea you had. But, same error when it works for me, and someone else runs it with a non ISO date format.

Yeah, tried that. Same error... One sec, I'll show you.

thats more like it

Same error...?

Wed Jan 01 040000 PST 2020 is new Date("2020-01-01T120000.000Z").toString()

Right... Bu, NetSuite is trying to use the client format, for server side code... 😕

same error, but i wouldnt expect to get an ISO-8601 string as the format if you used a Date

Right, but that is my UI format. If I set it to write that format, it works perfect for me. But, when someone else runs the script, witha different UI date format, and it breaks. That's what I mean by I've never had this happen before. The client side formats are being used on the server side, which I've never had happen...???

scripts use the format of the current user

Which means that this can never work now... I can't know what date format some rando decides to use... lol

N/format will format a Date to a string in the current user's settings

Example of a working Date filter, a

Date

passed in to `N/format.format`:

["custrecord_billend" , search.Operator.ON,format.format({value: new Date(), type: format.Type.DATE})]

that one will work, but wont include time

Little simpler since it's just using the current timestamp, but as long as you can get a correct

Date

object, you should just be able to use

N/format.format

Datetime includes seconds, which is not the request format

Nah, tried format as well, no luck. The date has to be 2020-01-01, not the current date...

The concept still applies

I'll try it again, before saying it doesn work... 🙂

The general idea is: 1. Turn the incoming date representation into a

Date

instance representing the correct timestamp 2. Use

N/format.format

to turn the

Date

instance into a string as the

format()

method automatically uses the current user's (or system's) date format preference

im not disagreeing what that, but there is no type that will output a datetime string without seconds

wow, that one really doesn't work... lol... ["notedate",search.Operator.ONORAFTER,format.format({value:new Date("2020-01-01"),type:format.Type.DATE})] = {"type":"error.SuiteScriptError","name":"INVALID_DATE_VALUE_1_MUST_MATCH_2","message":"Invalid date value NaN-NaN-NaN (must match yy-MM-dd h:mm a)","stack":["crea

it will work if you use ["notedate",search.Operator.ONORAFTER,format.format({value:new Date("2020-01-01T120000.000Z"),type:format.Type.DATE})]

The problem that I'm having is that I have to get data that is after the first only. And, that is causing an issue becuase I don't knwo what format every person is apparently using... 😕 Ahh, yeah, that's the way I had it previously... I'll try again...

I suppose I've never run into the issue with seconds. Generally when I'm working with dates, I'm using

moment.js

, and it's a matter of `format.format(moment(...).toDate())`whether there's a Time involved or not

Okay, now we are back to where it works for me... I'll try switching my format and see if it still works... 🙂 Maybe there was just a typo... #fingerscrossed