Apparently there is a design flaw in the current employer and job title fields in Civi.

"If you enter or amend these fields through the edit of a contact, a corresponding employment relationship will be established. Unfortunately, if you create an employment relationship directly then the two fields do not get updated. Likewise, if an employment relationship becomes non current or is deleted, then the two fields do not get updated."

Does anyone know about this and how can I get around it? I am entering job titles for contacts. Civi says it saves them. When I open the contacts the next day, the updates have not occurred.

  • Can you clarify what you mean by: Unfortunately, if you create an employment relationship directly then the two fields do not get updated.
    – themak
    Commented Feb 4, 2020 at 23:21
  • A lot of our contacts have the job title field blank. I have been updating this field for many contacts. It says that Civi has saved it, but I go in the next day and it is blank again. Because of the alleged design flaw you have to update the job title field through the "employee of" relationship. I have tried this but it does not seem to work. I don't understand why you cannot update a key field by editing the contact directly. Commented Feb 4, 2020 at 23:32
  • Do you have an extension installed or something that is related? Normally job title and employer are completely separate fields, and there isn't even a field or option to update job title from the relationship.
    – Demerit
    Commented Feb 4, 2020 at 23:35
  • We have no extensions installed. Apparently when you update the Employee Of field you put the job title in the description. I have told that the job title field will not update because of a design flaw in Civi. I presume that people in the Civi community would know about this. Commented Feb 4, 2020 at 23:37
  • Can you take screenshot? I just tried this in dmaster - everything worked correctly. Former job titles do not save - if you update the job title - it replaces whatever was there originally. As for employer - that's working correctly too.
    – themak
    Commented Feb 4, 2020 at 23:42

2 Answers 2


My experience is that 'Employer' field does get populated after adding the relationship directly. However the Job Title field is not related to the relationship and that wouldn't get populated, as it's a field on the contact record only.


Surely the point here is that the Job Title field should be linked to the Employee/Employer relationship record and not the contact record. In cases where an individual may have more than one employee relationship, they will also quite likely have different job titles in each context. This is a case of confusion for at least one org that I work with.

The Current Employer field is another weird one. It does not get auto-populated if an employee/employer relationship is created, but if a current employer is manually added, and a matching relationship record doesn't exist, one does get created. Current Employer implies that there can be only one, which is of course nonsense. Probably should be able to be turned off on a preferences page.

  • 1
    I concur with your points about connecting Job Title to the relationship, and the concept of a single current employment. That said perhaps some clarification re 'current employer' (for benefit of others unless i am misrecalling). The 'current employer' does get set when adding via the Contact Summary screen. It does get added eg via the 'On behalf of Org' option on Contribution pages. When 'add relationship' is used, then it is available as an option (and preset as ticked) once 'employee of' is chosen (at least that is what i observe today on dmaster)
    – petednz - fuzion
    Commented Jan 14, 2022 at 22:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.