Answers.Body: <p>When you pull the contact ID as a field in the view (even before you replace it), to what is the thousands marker field set?  I believe the default setting is comma (see <a href="http://screencast.com/t/8tiEiqVOBG" rel="nofollow">http://screencast.com/t/8tiEiqVOBG</a> ) - you might check that and change it to "none" if that is the case, to see if that makes a difference.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-18T16:35:49.827Z
Answers.Text: Perfect! Yes that was exactly it, all sorted thanks!
Answers.UserDisplayName: Tim Redman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-19T18:34:16.213Z
Answers.Text: there has been a long running argument within Drupal Views to stop the comma being default as it affects all such numeric fields.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-18T16:11:29.353Z
Answers.LastActivityDate: 2016-02-18T16:11:29.353Z
Answers.UserDisplayName: Lesley Carter - BackOffice
Body: <p>Within Drupal Views integrations creating a view of contacts, the Replacement Pattern "[id] == CiviCRM Contacts: Contact ID" inserts commas when a contact_id is greater than 999 - surely this is incorrect behaviour? Does anyone have a work around for this?</p>
  
Tags: <drupal><drupal-views>
Title: Drupal views integration ContactID inserts commas into number
ThreadText: # Drupal views integration ContactID inserts commas into number
  
  (Asked by: username_0 on 2016-02-18)
  
  Within Drupal Views integrations creating a view of contacts, the Replacement Pattern "[id] == CiviCRM Contacts: Contact ID" inserts commas when a contact\_id is greater than 999 - surely this is incorrect behaviour? Does anyone have a work around for this?
  
  **Tags:** drupal, drupal-views
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-02-18. Score: 2 | Accepted answer
  
  When you pull the contact ID as a field in the view (even before you replace it), to what is the thousands marker field set? I believe the default setting is comma (see <http://screencast.com/t/8tiEiqVOBG> ) - you might check that and change it to "none" if that is the case, to see if that makes a difference.
  
  > **Comments:**
  > **username_0**: Perfect! Yes that was exactly it, all sorted thanks!  
  > **username_2**: there has been a long running argument within Drupal Views to stop the comma being default as it affects all such numeric fields.  
  
  ---
  
  