Resolution: Won't Fix
Affects Version/s: None
Fix Version/s: Unscheduled
Currently, some commonly used date formats are reported as INVALID by the Import validation. For now, this only affects custom field import. However, as we add support for importing other classes of objects like activity_history - this will become a bigger issue.
Example: 8/23/2005 (in a default US localised site)
1. Clarify the rules that are used for validating Date type Custom Fields during IMPORT
2. Figure out best way to support a reasonable set of date format variations - given localisation variables and usage. We should check commonly used output formats in applications which are likely sources of import data - e.g. Yahoo, Outlook, census file samples etc.
3. Implement new 'rules'.