Households can be disabled globally by disabling that contact type. This is not exposed to the UI but is still pretty easy to do:
From the api explorer (Support -> Developer -> Api Explorer) make the following selections:
With a direct sql query:
UPDATE civicrm_contact_type SET is_active = 0 WHERE name = 'Household';
Note: there may be a few places left ...
To remove households from the interface completely:
Delete any households that may have been created and any relationships involving households (shared addresses, Household members, etc).
Update the civicrm_contact_type table in the CIVI database to set the active flag for 'Household' to 0 (as per Coleman's answer)
Update the civicrm_relationship_type table ...
The short answer:
When you want to store information about two people (e.g. "John Smith" and "Mary Smith") together, create a new household.
You can name the household whatever you like (e.g. "John and Mary Smith", or "Mary Smith and John Smith", etc)
Add shared information like home phone number (land line) and home address to the household record.
We have been going over this a lot with my fundraising team, trying to find a happy medium. When generating labels or PDF letters for one per household, be sure to create labels with only households. Then, you can even create a smart group that consists of individuals that are also part of a household and exclude that group from the rest of the "individuals" ...
If you are using Drupal as your CMS, then the answer is "yes". The drupal Webform-CiviCRM Integration module allows you to set up a form to register one or more people for any number of events, with full control over creating relationships, sharing addresses, sending a concise email recipt, and customizing the look and feel of your form.
For more ...
We tend to:
not use households but use individual memberships and the inheritance feature to construct Family (Household-like) Memberships
use Drupal Webform CiviCRM module to make this a one form signup (adults + children on one form) - with Webform CiviCRM you can add more then one Contact on the Form and specify relationships between these
We have setup a webform which enables the creation (or updating existing information) of
1) a household with its own data (phone number and physical/mailing address)
2) one or two adults with their own data (defaulting to our Spouse/Spouse relationship) and makes them share the address of the Household
3) 1-5 children with their own data who share the ...
Here is an extension that automatically creates a soft credit. I use it with my org and it works great. I'm running 4.7.2 with drupal 7.
Drupal users can (should) only be associated with an individual contact record but with a correctly set up 'on behalf of' workflow this can allow for an Individual to purchase a membership on behalf of an organisation. (I say 'should' because I know users have overridden this and hence permitted the Drupal user to have a uf_match link to the Org record)
If the households and individuals exist in the database but individuals do not have a shared address with the household, you can run the following sql to create a csv that you can import.
On the import use update and link the first 7 columns to the appropriate columns. (If you don't link the street address, city, state, etc., the individual's shown address ...
A workaround is to import the address along with the Master Address ID. So import like you are importing a new address but also include the Master Address ID, mapped to the "Master Address Belongs To" field. It links them and populates the address.
Sean describes the 'text book' answer well but depending on your usage, there are other options you could consider:
1) If you want to stick closely to your old system you could add custom fields for the spouse/partner name. Customise the Addressee field as Kainuk suggests for mailings.
Assuming 'John Smith' is the main contact and 'Mary Smith' is in the ...
Late, but thought household aggregate contribution report might be helpful to some searchers.
We use up to three records for a couple. Event info goes on individual record and gifts generally go on a household record. Some gifts will be on an individual record before we knew of spouse or for raffle ticket purchases (where our state's DOJ allows - and ...
You need to provide same set of values to create address for members of the household with additional parameter master_id as Address foreign key id of household contact.
$addressParams = [
'sequential' => 1,
'contact_id' => $householdContact['id'],
'location_type_id' => "Home",
'is_primary' => 1,
'street_address' => $form_state['...
There is a Contributions by Household report available under Reports > Contribution Reports by default in CiviCRM. This should provide at least the basics of what you need. You may need to edit the filter criteria to set "Household Member is" as the Relationship Type rather than "Head of Household is".
This has been confirmed as bug CRM-16588. Please consider marking this as the accepted answer, so that future Stack Exchange users with this issue can find the bug status to identify when the bug has been fixed.
I do something very similar with my church. the actual donation is credited to the individual who made it with a soft credit going to the household. This allows us to do reporting by either household or individual.
Your dedupe rules aren't probably tight enough so instead of seeing that the contact exists already, it creates a new one.
The fact that your getting dups also probably says you are doing multiple imports with the same CVS. When I do imports I often do run the same file more than once, but the key difference is if the contact already exists and you are ...
You can disable contact-types directly in the db or with the api, but a word of caution: I've seen older sites where people have messed with the basic contact types, and they've had real problems.
Based on other answers, this may be safer to do in current versions of CiviCRM, but I recommend thorough testing of any changes you make.
In re-reading your question, we also came up with a jQuery solution for creating the Household Name from the names of the Parent and Spouse.
We added a class to the Parent First Name field, Parent Last Name field, the Spouse field, and the Household Name field (through the webform field UI itself, not on the Webform-CiviCRM section). (In our context most ...
It sounds like it will depend somewhat on your set up. If you're on Drupal, you could have a look into using webform civicrm which would be able to handle all of the above (creating the contacts, relationships, and membership). You could also do clever things like populate the name of the Household based on the Last name value entered for one of your ...
It is a great idea. Using CiviRules, you could get a good bit of the way there out of the box. To set the soft credit though, you would need to (or pay someone to) write some code -- you'd have to code the CiviRule action.
For the formula, you'd set the trigger to "Contribution is added."
For the conditions, you could have a couple:
"Contribution is (not)...
you would have to check how complete the turkish translation is. It seems we have achieved 100% translated, but can't judge of the quality of the translation.
They are various hosting providers that can offer you to host. We do host on our own servers, so don't have a first hand experience on what they offer and ...
We are a church and use Households to hold the address and to aggregate contributions.
We use the extension https://github.com/PalanteJon/coop.palantetech.module.automaticsoftcredit to automatically create soft credits to the household for all individual contributions. In my opinion this is how Civi should work out of the box (rather than allowing a ...