Answers.Body: <p>Ok - so stroke of luck - was checking the Contact table and spotted that one of my problem patients had 'array' in the Preferred Communications table, as did the other record which the import failed on. As did about another dozen.</p>
  
  <p>Once I changed the value in the db i could then visit the record.</p>
  
  <p>Which I guess poses another question of how did they get array in as the value and I may post that as a separate question.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-21T01:38:26.320Z
Answers.Text: Something that happens occasionally with Excel CSV files, particularly if they‘ve also been edited by hand is that they get their ,,,,,,s confused along with its ""s. So I bet that the value that you wanted got uploaded as ""100,"" or "100," not just "100", which would explain why it was interpreted as an array. #Theory
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-21T02:24:25.270Z
Answers.Text: nope - maybe haven't explained well enough -  data that is borked on the contact record is not part of the import - the contacts data was corrupted in that field pre-import somehow - so it may possibly been a result of an earlier import but civi should prevent incorrect data being uploaded
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-21T05:43:09.487Z
Answers.Text: so yes you could be exactly right, ie that their Comms Prefs were imported as you say, with a comma, some time in the past - not sure i can check beyond looking in logs but those records only had 'array' in their histories. i guess the old import upload files may be on their site too. not sure if they can be bothered with more digging ;-)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-21T11:41:55.653Z
Answers.Text: Definitely look in logs. And I wish I‘d have added this as an answer for points :(
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-21T20:36:12.963Z
Answers.Text: you still can ;-)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-21T20:52:34.193Z
Answers.Text: though am wondering, if it had happened via an import would the result of importing '3,' in to Pref Comms field have been allowed, and would it have resulted in the word Array showing in that field (in the db)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-22T00:02:06.717Z
Answers.Text: Done - give me points!!!
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-20T21:58:52.013Z
Answers.LastActivityDate: 2016-03-20T21:58:52.013Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <blockquote>
  <p>Something that happens occasionally with Excel CSV files, particularly
  if they‘ve also been edited by hand is that they get their ,,,,,,s
  confused along with its &quot;&quot;s. So I bet that the value that you wanted
  got uploaded as &quot;&quot;100,&quot;&quot; or &quot;100,&quot; not just &quot;100&quot;, which would explain
  why it was interpreted as an array. #Theory</p>
  <p>Definitely look in logs.</p>
  </blockquote>
  <p>To answer more comments in the previous thread:</p>
  <p>echo $array results in the word Array being output, so it wouldn't surprise me if there were other bits of PHP that do the same. Parts may even call the echo function frankly.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-21T21:54:32.493Z
Answers.LastActivityDate: 2016-03-21T21:54:32.493Z
Answers.LastEditDate: 2020-06-17T09:00:50.810Z
Answers.UserDisplayName: JohnFF
Body: <p>As per the title - this message was observed first during an import, which failed. I re-imported with a 'tracker' field so i could see exactly where it failed. And rinsed and repeated. Found 2 records in import that were tripping it up. When trying to visit those records in civicrm i got same error, and with backtrace got</p>
  
  <p>/sites/all/modules/civicrm/CRM/Utils/Type.php(362): CRM_Core_Error::fatal("One of parameters  (value: Array) is not of the type Integer")</p>
  
  <p>but does that help identify the culprit data?</p>
  
Tags: <import><error><core>
Title: One of parameters (value: Array) is not of the type Integer - initially observed during import, but same when visiting Contact Record
ThreadText: # One of parameters (value: Array) is not of the type Integer - initially observed during import, but same when visiting Contact Record
  
  (Asked by: username_0 on 2016-03-20)
  
  As per the title - this message was observed first during an import, which failed. I re-imported with a 'tracker' field so i could see exactly where it failed. And rinsed and repeated. Found 2 records in import that were tripping it up. When trying to visit those records in civicrm i got same error, and with backtrace got
  
  /sites/all/modules/civicrm/CRM/Utils/Type.php(362): CRM\_Core\_Error::fatal("One of parameters (value: Array) is not of the type Integer")
  
  but does that help identify the culprit data?
  
  **Tags:** import, error, core
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2016-03-20. Score: 2
  
  Ok - so stroke of luck - was checking the Contact table and spotted that one of my problem patients had 'array' in the Preferred Communications table, as did the other record which the import failed on. As did about another dozen.
  
  Once I changed the value in the db i could then visit the record.
  
  Which I guess poses another question of how did they get array in as the value and I may post that as a separate question.
  
  > **Comments:**
  > **username_1**: Something that happens occasionally with Excel CSV files, particularly if they‘ve also been edited by hand is that they get their ,,,,,,s confused along with its ""s. So I bet that the value that you wanted got uploaded as ""100,"" or "100," not just "100", which would explain why it was interpreted as an array. #Theory  
  > **username_0**: nope - maybe haven't explained well enough -  data that is borked on the contact record is not part of the import - the contacts data was corrupted in that field pre-import somehow - so it may possibly been a result of an earlier import but civi should prevent incorrect data being uploaded  
  > **username_0**: so yes you could be exactly right, ie that their Comms Prefs were imported as you say, with a comma, some time in the past - not sure i can check beyond looking in logs but those records only had 'array' in their histories. i guess the old import upload files may be on their site too. not sure if they can be bothered with more digging ;-)  
  > **username_1**: Definitely look in logs. And I wish I‘d have added this as an answer for points :(  
  > **username_0**: you still can ;-)  
  > **username_0**: though am wondering, if it had happened via an import would the result of importing '3,' in to Pref Comms field have been allowed, and would it have resulted in the word Array showing in that field (in the db)  
  > **username_1**: Done - give me points!!!  
  
  ---
  
  ### Answer by username_1 on 2016-03-21. Score: 1
  
  > Something that happens occasionally with Excel CSV files, particularly
  > if they‘ve also been edited by hand is that they get their ,,,,,,s
  > confused along with its ""s. So I bet that the value that you wanted
  > got uploaded as ""100,"" or "100," not just "100", which would explain
  > why it was interpreted as an array. #Theory
  >
  > Definitely look in logs.
  
  To answer more comments in the previous thread:
  
  echo $array results in the word Array being output, so it wouldn't surprise me if there were other bits of PHP that do the same. Parts may even call the echo function frankly.
  
  
  ---
  
  