CiviCRM Community Forums (archive)

Hi All,

We have been using CiviCRM for a while now. Started by setting up too many contact sub-types and too many types of relationships.

Now realizing that we want organizations to have 1 simple relationship to their different types of employees, the stock employer/employee relationship. This relationship is useful, because it can be used in creating mailing labels.

We use the 'Relationships' tab as an index of an organizations employees. To see the employee's job, we added custom relationships which describe the job, effectively duplicating the 'Job Title' field. And if we want the stock employer/employee relationship (which we now realize we DO want), it creates duplicate entries on the 'Current Relationship' table (one employer/employee, one job for/job of).

It is much simpler to add a new 'Position' column to the 'Current Relationship' table that shows the employee's 'Job Title'.

No maintaining a crazy list of relationship types that are redundant to the 'Job Title' field. Quicker entry of individual records. Much better. Nice clean listing when you open the tab to see your index of employees. Ability to print custom mailing labels containing the employer token.

Apply the patch to civiCRM 3.4.5: civicrm/Templates/CRM/Contact/Page/View/Relationship.tpl

And the change is so simple that if your version is totally different, you just read the .txt file, look at the 4 minor changes, and edit by hand.

Yes, the 'Position' shows up when looking at a household's relationships. So what. I'd rather have the 'Position' show up when looking at both households and organizations, than not have it show up at all...

GF