CRM

carlyejowens
Participant

Property value '1535526000000' isn't valid (details: 1535526000000 is at 7:0:0.0 UTC, not midnight!)

SOLVE

When trying to import contact lists today, I keep getting the error "Property value '1535526000000' isn't valid (details: 1535526000000 is at 7:0:0.0 UTC, not midnight!)".  I do have a column with dates, but no time stamps.  This error is preventing me from importing any lists.

 

Simply copying and pasting the entire spreadsheet into a fresh file seems to solve the problem, but even then, I'm sometimes getting a separate error "Can't process date '43341' using MDY format (from column 'last_campaign_date')".  Last campaign date is the date field I referred to, but that is definitely not the contents.  It's a date formatted as a date (8/29/2018).  It returned the exact same error for every row in the spreadsheet.  I import lists like this every day and have never seen errors like this before.

0 Upvotes
1 Accepted solution
jennysowyrda
Solution
Community Manager
Community Manager

Property value '1535526000000' isn't valid (details: 1535526000000 is at 7:0:0.0 UTC, not midnight!)

SOLVE

Hi @carlyejowens,

 

Are you still experiencing this issue? If so, can you please share screenshots of where you are encountering this error message? 

 

If you did resolve the issue, do you mind sharing your findings with the Community? 

 

Thanks, 
Jenny

View solution in original post

0 Upvotes
2 Replies 2
jennysowyrda
Solution
Community Manager
Community Manager

Property value '1535526000000' isn't valid (details: 1535526000000 is at 7:0:0.0 UTC, not midnight!)

SOLVE

Hi @carlyejowens,

 

Are you still experiencing this issue? If so, can you please share screenshots of where you are encountering this error message? 

 

If you did resolve the issue, do you mind sharing your findings with the Community? 

 

Thanks, 
Jenny

0 Upvotes
carlyejowens
Participant

Property value '1535526000000' isn't valid (details: 1535526000000 is at 7:0:0.0 UTC, not midnight!)

SOLVE

It seems like it was a temporary bug.  I'm not seeing it anymore.

0 Upvotes