Answers.Body: <p>I don't think anything has changed.  Every participant status has both a label/name as well as an assigned ID (integer) value.  The search builder lets you construct a search using either construct.</p>
  
  <p>I do see on the 4.6 sandbox, that when I select to search on Participant Status ID that its possible option values are the names rather than the ID's.... however the result set still came back correctly and displayed the ID's.</p>
  
  <p>I suspect this behaviour goes back to v3 days.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-19T18:15:56.580Z
Answers.LastActivityDate: 2015-06-19T18:15:56.580Z
Answers.UserDisplayName: DaveD
Body: <p>Did I miss something or has there been a architectural change with these parameters? The search builder gives a list of the status options for both of these parameters, but for the Participant Status ID is throws an error: is not of the type Int</p>
  
  <p>In which release has there been recent changes to this part of civicrm? And which Github or JIRA issues document that change?</p>
  
Tags: <civireport>
Title: Participant Status vs. Participant Status ID
ThreadText: # Participant Status vs. Participant Status ID
  
  (Asked by: username_0 on 2015-06-19)
  
  Did I miss something or has there been a architectural change with these parameters? The search builder gives a list of the status options for both of these parameters, but for the Participant Status ID is throws an error: is not of the type Int
  
  In which release has there been recent changes to this part of civicrm? And which Github or JIRA issues document that change?
  
  **Tags:** civireport
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-06-19. Score: 1
  
  I don't think anything has changed. Every participant status has both a label/name as well as an assigned ID (integer) value. The search builder lets you construct a search using either construct.
  
  I do see on the 4.6 sandbox, that when I select to search on Participant Status ID that its possible option values are the names rather than the ID's.... however the result set still came back correctly and displayed the ID's.
  
  I suspect this behaviour goes back to v3 days.
  
  
  ---
  
  