Answers.Body: <p>I think Demerit's answer of adding org-to-individual should work.  However, i'd thought i'd add some other considerations for anyone searching. </p>
  
  <p>I've had this problem before, especially when using multi-client case setup.  </p>
  
  <p>I found that if there was a mismatch between any of the clients contact type/subtype with the new caseworker's contact type/subtype then i got this message.  </p>
  
  <p>This was further compounded by some users trying to add invalid contacts (e.g. a household) as clients to the case.  </p>
  
  <p>Steps to check</p>
  
  <ul>
  <li>Contact type/subtype of each client(s) involved in a case </li>
  <li>Contact type/subtype of the new case manager </li>
  <li>Check all combinations are valid</li>
  <li>If you're doing this with bulk import data there could be an issue missing data e.g. contact subtype. </li>
  </ul>
  
  <p>I found the solution by </p>
  
  <ol>
  <li>reviewing relationship types <strong>Administer >> Option Lists >> Relationship Types</strong> </li>
  <li>Setting them to <strong>individual - individual</strong> (they were 
  the more narrow <strong>"contact sub-type A - contact sub-type B")</strong>.  This lessend the chance of a conflict</li>
  <li>Amend the case open form or webform to limit the contact types that can be added as clients to limit only to valid contact types. </li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-01T10:21:38.183Z
Answers.LastActivityDate: 2017-02-01T10:21:38.183Z
Answers.UserDisplayName: Bruce
Answers.Body: <p>Is your client an organization or individual? I know at one time it only worked with individual-individual, but I thought that was updated, but maybe not. I get the same error when I try on the public demo (4.6) with an org client.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-10T10:42:22.217Z
Answers.Text: it is an organisation
Answers.UserDisplayName: Oliver
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-11T14:32:42.597Z
Answers.Text: Try adding a new relationship type that is org-to-individual and updating the civicase config to use it for the manager.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-05T18:51:08.280Z
Answers.LastActivityDate: 2016-02-05T18:51:08.280Z
Answers.UserDisplayName: Demerit
Body: <p>I try to change the role of a case.
   - Case coordinator (case manager) is manuel berger.
   - I click on reassign case coordinator
   - Enter a new name and click save</p>
  
  <p>then the following error massage appears:
  "The relationship type definition for the case role is not valid for the client and / or staff contact types. You can review and edit relationship types at Administer >> Option Lists >> Relationship Types.</p>
  
  <p>Is there a solution to change?</p>
  
  <p>Thanks.</p>
  
Tags: <civicase>
Title: cases - change case roles
ThreadText: # cases - change case roles
  
  (Asked by: username_0 on 2016-02-05)
  
  I try to change the role of a case.
  - Case coordinator (case manager) is manuel berger.
  - I click on reassign case coordinator
  - Enter a new name and click save
  
  then the following error massage appears:
  "The relationship type definition for the case role is not valid for the client and / or staff contact types. You can review and edit relationship types at Administer >> Option Lists >> Relationship Types.
  
  Is there a solution to change?
  
  Thanks.
  
  **Tags:** civicase
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-02-01. Score: 3
  
  I think username_2's answer of adding org-to-individual should work. However, i'd thought i'd add some other considerations for anyone searching.
  
  I've had this problem before, especially when using multi-client case setup.
  
  I found that if there was a mismatch between any of the clients contact type/subtype with the new caseworker's contact type/subtype then i got this message.
  
  This was further compounded by some users trying to add invalid contacts (e.g. a household) as clients to the case.
  
  Steps to check
  
  * Contact type/subtype of each client(s) involved in a case
  * Contact type/subtype of the new case manager
  * Check all combinations are valid
  * If you're doing this with bulk import data there could be an issue missing data e.g. contact subtype.
  
  I found the solution by
  
  1. reviewing relationship types **Administer >> Option Lists >> Relationship Types**
  2. Setting them to **individual - individual** (they were
     the more narrow **"contact sub-type A - contact sub-type B")**. This lessend the chance of a conflict
  3. Amend the case open form or webform to limit the contact types that can be added as clients to limit only to valid contact types.
  
  
  ---
  
  ### Answer by username_2 on 2016-02-05. Score: 3
  
  Is your client an organization or individual? I know at one time it only worked with individual-individual, but I thought that was updated, but maybe not. I get the same error when I try on the public demo (4.6) with an org client.
  
  > **Comments:**
  > **username_0**: it is an organisation  
  > **username_2**: Try adding a new relationship type that is org-to-individual and updating the civicase config to use it for the manager.  
  
  ---
  
  