Relationship validation

Brainstorming a counter argument to the assumption that a relationship can't be between one Contact and itself...

Imagine a doctor's office with a Relationship "financially responsible for".

JD is financially responsible for JD
JD is financially responsible for Laura
JD is financially responsible for Ramona
JD is financially responsible for Sam

This wouldn't necessarily flow through a Household and could involve the proposed forbidden relationship.

Perhaps instead of limiting the relationship, there should be a warning to catch accidents but allow these sorts of exceptions.

It seems like a corner case. Is this something you are planning to use?

It is possible to make it a setting on the relationship bundle.

It would not make sense to allow the same contact in a parent-child relationship.

If it is allowed, the form should make the user confirm, or otherwise indicate that the same contact is selected.

None of the relationship types so far should allow the same contact.

I am reluctant to add a setting at this time. I will think about it.

Not a use case I'm expecting to encounter personally. I'm just playing devil's advocate in an effort to avoid potential problems caused by validation.

Thinking through a hypothetical setting on the Relationship, I would suggest that it default to preventing a relationship to oneself. It could even be hidden during Relationship creation and only be visible when editing a Relationship to support the option without cluttering the main flow, but I don't think it makes much difference.

Adds possible validation method.