CiviCRM has multiple location types ("home", "work", "postal", "billing").
The contact DB I'm working with has no distinction, and the types don't add value for this contact. The location types were renamed as "Location 1", "Location 2", etc during data import. The client desires to eliminate the need to choose a given location type.
I believe there are some parts of CiviCRM which still expect a dedicated "Billing" location type, however (eg search for CRM_Core_BAO_LocationType::getBilling()).
- What expectations does CiviCRM make about a dedicated Billing address type? AFAICT, this is somewhat "magic" in that
CRM_Core_BAO_LocationType::getBilling()looks for a location type with a name of "Billing". - What issues arise if the Billing location type is renamed or deleted?
- What other considerations might there be when modifying CiviCRM's builtin location types?
