Answers.Body: <p>For the moment, the best workaround is to edit the activity dates in the CSV to have four-digit years before importing.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-18T20:28:54.520Z
Answers.LastActivityDate: 2022-01-18T20:28:54.520Z
Answers.UserDisplayName: Noah Miller
Body: <p>When I import activities from a CSV using a date format that includes a 2-digit year (for example, mm/dd/yy), dates such as &quot;01/18/22&quot; get imported as January 18, 1922 instead of January 18, 2022.</p>
  <p>It looks like years from 00 to 20 are assumed to be in the 21st century (2000-2020), but 21-99 are assumed to be in the 20th century (1921-1999).</p>
  <p>How can I work around this?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-01-19T03:14:05.817Z
Comments.Text: have you modified any of the date settings at /civicrm/admin/setting/preferences/date?reset=1
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-01-19T21:20:37.180Z
Comments.Text: The date preferences have no effect on this currently (CiviCRM 5.46). See a proposal to fix it: https://lab.civicrm.org/dev/core/-/issues/3037
Comments.UserDisplayName: Noah Miller
Tags: <import><activities><activity><dates><data-import>
Title: Activity import gets the century wrong
ThreadText: # Activity import gets the century wrong
  
  (Asked by: username_0 on 2022-01-18)
  
  When I import activities from a CSV using a date format that includes a 2-digit year (for example, mm/dd/yy), dates such as "01/18/22" get imported as January 18, 1922 instead of January 18, 2022.
  
  It looks like years from 00 to 20 are assumed to be in the 21st century (2000-2020), but 21-99 are assumed to be in the 20th century (1921-1999).
  
  How can I work around this?
  
  **Tags:** import, activities, activity, dates, data-import
  
  > **Comments:**
  > **username_1**: have you modified any of the date settings at /civicrm/admin/setting/preferences/date?reset=1  
  > **username_0**: The date preferences have no effect on this currently (CiviCRM 5.46). See a proposal to fix it: https://lab.civicrm.org/dev/core/-/issues/3037  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2022-01-18. Score: 1
  
  For the moment, the best workaround is to edit the activity dates in the CSV to have four-digit years before importing.
  
  
  ---
  
  