Currently addresses and telephone numbers are independent of each other in how this module works.
But often telephone numbers will be linked to an address. it would be able to group them if that is the case.
Currently addresses and telephone numbers are independent of each other in how this module works.
But often telephone numbers will be linked to an address. it would be able to group them if that is the case.
Comments
Comment #2
jdleonardI think this might be an example of the type of data that would be best suited to being stored for a Household Contact entity. Typically the phone number is moreso related to a household than to the address itself.
There is perhaps a need to more easily expose the contact methods for a Household Contact on the Contact records for each household member.
Could you please share details of your use case?
Comment #3
naheemsays commentedI am exploring making a multi-correspondent system to track correspondence, documents and time. I came across crm and crm_case which seem to be extremely relevant and similar to what I am looking for.
I wasnt able to see any UI for linking the household to individuals so apologies if i have missed this feature.
For the bigger picture, on the crm_case module I want to create a field for multiple correspondent groups for a law firm type of set up.
Solicitors can have multiple offices for one firm - each with its own address and contact details. The current CMS we use has individual correspondents for each of them, similar to crm's contact module. I was pondering over the ability to merge them into one where the head office and side offices are under one contact with tokens to refer to the relevant offices. I don't know if that is a superior solution or not.
A more complicated contact type is insurance companies. Their head office is often abroad in some tax haven that will not deal with correspondence and they will have correspondence offices in the UK with multiple sub offices depending on the type of contact (own insurer vs claiming against other sides insurer etc). I was looking how to model this. relationships between the various contact may be the way with the head office as the so called "household" in the current default config.
For completeness and mostly unrelated to this issue: When i get to it there is a second level of relationship that I will be looking for as well: on the case level where the client or other party and its insurers solicitors and brokers can be mapped at the case lever.
The plan is for a field to have clients (autofilled from the current contact that is entered into the case for now), other parties that can have multiple contacts that are insurers, insurance brokers or solicitors. along with each of them having separate fields for contact/custom name, number and email address.
Then there will be correspondents for experts (single contact details) and places to obtain documents (say HMRC or DVLA or local Council).
Comment #4
jdleonardThe standard way to link a Contact to another Contact is to create a Relationship.
More (developer-oriented) information than you probably want about them: https://project.pages.drupalcode.org/crm/entity/relationship/
You can manage the Relationship Types via Structure -> CRM and the relationship entities themselves via CRM -> Relationships.
Thank you for sharing your use case. I'll respond more when I have time to digest it properly. In the meantime, classifying this as a support request until it is clear that there's a need for a feature.
Comment #5
jdleonardBelatedly getting back to this.
One approach to representing a subsidiary or (sub)office of an Organization would be as an additional Organization, related via a Relationship of an aptly named type. This would provide a natural way to group emails/phones related to a given office: as that office's Organization entity's Contact Methods.
Please re-open this issue if you wish to discuss further.