if i have a date in JSON stringified fashion from a client script (Eastern Time Zone) feeding into a Suitelet, and the Suitelet is running in a different time zone (Pacific), dates will be backdated by 1 day. There has to be an elegant solution to this. Anyone? Sample: Client fed value of

2021-11-02T04:00:00.000Z

(JSON stringified) Suitelet processes, converts string to date (

new Date(2021-11-02T04:00:00.000Z)

), end up with

Mon Nov 01 2021 21:00:00 GMT-0700 (PDT)

date object. I can parse 2021-11-02 from the original JSON stringified string and create a string

11/02/2021

and create a new Date from there, but is there any more elegant approach?

If you are using the Date with one of record apis to set a value, then you can probably just use the Date as is

here the client is reading in the date into a string (with other info in there), where it is then stringified and passed to a Suitelet… so I don’t have a Date object

you used the Date constructor to change your iso-8601 string into a date

The Date input on screen is really “11/2/2021” (as it is not a datetime input, rather date); the client renders that as 0400… because I am in the Eastern timezone. So, technically, I only want the short date…

the date is correct, the string given represents Mon Nov 01 2021 210000 GMT-0700 (PDT)

Except it is incorrect bec it should have been the short date, really - see my previous response (crossed paths)

yes, so basically, capture it in the Client script - I was trying to avoid that. Also, that’s clunky - though we know where the data center is, i guess so i can fudge it by 3 hours

for suitelets you can usually just use the text you get from the field directly when setting fields on records

Correct - if you submit the Suitelet. In this case, the Client script was preparing a string (for some reason - beyond this scope) for processing. Thanks!