CiviCRM Community Forums (archive)

> One is that when I click "Add new role" in the Case Roles section, the drop down list in the pop-up has 5 relationships on the list - the last 5 in the civicrm_relationship_type table - but I've only used 4 of these in the xml file.

That's by design. The ones listed in the xml are prepopulated for that case type, and the add new role is to allow you to add others that aren't in the xml on the fly. To assign the role to a contact, click the icon in the right-hand column of the roles table.

> Also, choosing a relationship (role) doesn't cause the role to be assigned/relationship to be created.

That might be a bug. If it isn't appearing in the roles table after choosing it then it probably is. My first guess would be it's contact-type related. The initial civicase release only supported Individual-Individual and maybe this needs updating.

Well, some progress.  I can add a role using the button.  The roles table does not load the defined roles on a new case, though.  I notice a couple of things.  First, the configuration documentation says that the value in xml defined by <name> should be the name_a_b but I notice the the Adult Day Care sample xml that name_b_a is used.  I've gone into the database and set both of these fields to the same value for the CiviCase roles  - didn't help.  I've checked that all the names match the db as well.

Any tips?

Using version 3.1.3.  I am using contact sub-types.  Changing the relationships to just "individual" types enabled "add role" button.  I can repeat the issue you referenced with the sample case on my sandbox though...

Thanks for the help - I'll start digging into the code while we see if anyone else has ideas...

Good catch. Sounds like a bug. My guess is it was introduced when the label column was added which I think happened in 3.1 or maybe 3.0, and a name reference that should have stayed name got changed to label.

Did you find where in the code this is? I'll file in jira.

Thanks but typically that's not the intended behavior throughout civicrm.  "name" is like the key field that does not change, and is therefore used for lookups, whereas "label" is what end users see and can change as desired as thus is not a good candidate for lookups.