A CSV import already warned you about a date it could not read at all. But two
other cases still went by in silence:
- A date before 1900. Values like
06/01/1850usually mean a cell was
mis-typed or mis-read, so the importer refuses to store them on a contact.
It said nothing, and the contact quietly kept the time of the import as its
created date instead. - A date in the future. A created date in 2030 is moved back to the time of
the import. Nothing on the screen said the value had been changed, so the
date on the contact afterwards looked like the one you supplied.
In both cases the import reported a clean run, which is exactly the situation
where a lost date is hardest to notice.
What you may notice
The completion screen now lists a warning for each of these, naming the CSV
column and quoting your cell exactly as you wrote it — so you can find the row
in your own file. Warnings do not fail the row: the contact still imports with
everything else it carried.
What this doesn’t change
The rules themselves are the same. A pre-1900 date is still not stored, and a
future created date is still moved back to the import time. The only difference
is that you are now told about it.