We experience the same problem for some month now whilst using the date field in design manager 2.0. It's really annoying. I had opened a ticket month ago, but the problem was not solved until now.
Take your timezones standard deviation to UTC (e.g. CET = +1) and multiply that value with 3600000 (3600000ms = 1 hour). Finally put the result into an add filter like shown above.
Hubspot rendering incorrect date for timestamp value
@jsimone the closedate property is a datetime property, not just a date, so it can store any date with a time value. As mentioned above, datetime properties are displayed based on the time zone settings of your system, so you’ll see the date based on your system and not the time zone setting for the portal.
Hubspot rendering incorrect date for timestamp value
@brian we have two types of properties for storing time values, date and datetime.
date properties need to be set to midnight so that the same date is displayed regardless of the time zone.
datetime properties can store any time, and get displayed based on the timezone of the person viewing the record.
That last error was happening because that property is a date property (unlike the closedate which is a datetime), so that one needs to be set to midnight.
We have some more details about those property types here:
HubSpot API endpoints accept UNIX formatted timestamps in milliseconds. Most scripting languages have built-in functions or existing libraries that handle time conversion, but you must ensure that your timestamp values are in the correct UNIX...
Hubspot rendering incorrect date for timestamp value
Hi, what about this issue when using a CozyRoc API for the integration as REST Destination.
Any "date" given returns errors with different UTC (either 4 or 5) . Company Settings is currently in EST time (checked based on other post/forums).
I tried to convert the time already to datetime property with UTC consideration. But nothing (time differences).
Any idea? Thanks.
{"status":"error","message":"Errors found processing batch update","correlationId":"b14929fe-7bdb-4fc5-9adf-c7471807b026","invalidEmails":["(e-mail)mspizzadoe@aol.com"],"failureMessages":[{"index":0,"propertyValidationResult":{"isValid":false,"message":"-353966400000 is at 4:0:0.0 UTC, not midnight!","error":"INVALID_DATE","name":"owner_date_of_birth"}},{"index":0,"propertyValidationResult":{"isValid":false,"message":"1012539600000 is at 5:0:0.0 UTC, not midnight!","error":"INVALID_DATE","name":"last_funding_date"}},{"index":0,"propertyValidationResult":{"isValid":false,"message":"496987200000 is at 4:0:0.0 UTC, not midnight!","error":"INVALID_DATE","name":"business_start_date"}},{"index":0,"propertyValidationResult":{"isValid":false,"message":"1037595600000 is at 5:0:0.0 UTC, not midnight!","error":"INVALID_DATE","name":"payoff_date"}},{"index":0,"propertyValidationResult":{"isValid":false,"message":"996552000000 is at 4:0:0.0 UTC, not
Hubspot rendering incorrect date for timestamp value
@lightcap That is correct. The lists UI will only allow you to set a date, not a specific time. The lists system does support specific times internally, but If you need to use a specific timestamp, you’d need to use the Contact Lists API to update or create the list.
Hubspot rendering incorrect date for timestamp value
when I send over time value that is not corrected for UTC offset, i get:
“isValid”:false,“message”:“1480568400000 is at 5:0:0.0 UTC, not midnight!”,“error”:“INVALID_DATE”,“name”:“event_inquiry_submission_date”}],“requestId”:“a3ab39ec-6b29-4bad-8caa-e643b8af343c”
so the 5:00:00 comes from us being in EST.
the error returns: invalid date. still not sure how to proceed
The deal property closedate is a datetime property, not a date property. Date properties need to be set to midnight UTC for the date you want to use, but datetime properties store the time and date, and the date displayed will be the date that the set time represents, so if you want the 28th to be displayed, you’d need to use a timestamp that represents the 28th in your local timezone. You can see the full date and time in the history for the property.