Author Topic: Automatic relationship Household member (Read 504 times)

jaapjansma · September 05, 2013, 03:58:36 am

Today I was working on a migration script which havenly used the civi api.
I discovered the following feature/bug:

This is what I do with the API

Cretae household
Create address for household
Create an individual
Create an address for the individual, and set master_id to household address id.

Expected outcome:
- An household with an address
- An individual with a shared address of the household
- NO relationships between them because I haven't created the relationship

Real outcome
- An household with an address
- An individual with a shared a adress
- A relationship of type household member between the household and the individual

Is this correct? Or is this something which could be a feature but is in reality a bug?

When I unset the shared address the relationship is not created.

Coleman Watts · September 05, 2013, 08:32:57 am

I'd call this a feature rather than a bug. The api handles current employer the same way (if you share an address with an org it creates the relationship)

jaapjansma · September 05, 2013, 10:04:11 am

Thanks. That is good to know and comes in quite handy.

Eileen · September 05, 2013, 02:39:32 pm

unless there is a unit test for it it probably doesn't qualify as a feature as there are no guarantees it won't break in a future version.

CiviCRM Community Forums (archive)

News:

Author Topic: Automatic relationship Household member (Read 504 times)

jaapjansma

Automatic relationship Household member

Coleman Watts

Re: Automatic relationship Household member

jaapjansma

Re: Automatic relationship Household member

Eileen

Re: Automatic relationship Household member