CiviCRM Community Forums (archive)

I did some searches in the forum, and think I already know the answer to this. But just to confirm --
Am I correct that currently there is no way to export a list of individuals and ALSO include the organization to which they belong via relationships (e.g. the company they are employed by)?
-Brian

I took a look at BIRT, but don't think my shared hosting environment will support its requirements.

I went back in and was looking at the "current_employer" field, hoping that I could make that work for my needs. I figured at first it was just a standard field that required manual entry of data. But I couldn't find it in the table structure or ERD, so I started looking for it in the code.

In CRM/Contact/Form/Edit.php, that form field is populated based on whether there's an existing employer/employee relationship defined (if multiple it appears to select the most recently created organization). Interestingly, if you manually type into that current_employer field it will create the employer/employee relationship, and create an org record if the organization doesn't currently exist.

Anyway, what was the intent of creating that field besides being able to basically see the employer relationship on the edit form/summary tab? Has there been any effort to include that field in the export functions? Also seems like you'd want to make that a true table field, and use the existing functions to update the data in the field on form save, rather than simply make it a field that always dynamically shows the relationship defined elsewhere.

-Brian

You might want to check: http://issues.civicrm.org/jira/browse/CRM-1246

kurund

The "Current Employer" field is basically a shortcut to exposing/updating the latest "Employee of" relationship for an Individual. The data is stored in the civicrm_relationship table. Storing Employee-Employer relationships this way allows for tracking of a person's employment history, notes on the relationship etc.

We haven't addressed export of relationships as of yet because exports of 1:many structures is complicated and possibly not appropriate for CSV formatted outputs. That said, I suspect we'll do something to address the "most-used" relationships like Employer at some point.

In the meantime - some thoughts on your approach for hacking a solution:
- rather than modifying the schema, which potentially could cause upgrade problems etc. - might make more sense to store the Employer Name in a custom field
- I would probably leave the logic in for creating/updating the Employee of relationship - and add logic to ALSO store the Org Name in your custom field (basically a "copy" of the relationship data).  I think the value is present in the postProcess $params array - in which case you could just add a few lines to save that value to your "hard-coded" custom field.

That's an old post.
Current versions (v2.1+) export that field by default.

In v2.1+, the current employer is set on the main contact summary edit page.
Edit an individual. You'll see a current employer dropdown.

If the relationship to the org does not currently exist, selecting a current employer will create the relationship and set it to the current employer.

You have a situation where you have relationships created, but they have not been recorded as the current employer.

Did I missed a step?

When you import the contacts using a csv... isn't it enough to import the field "employee of" and CiviCRM will create a new record if it's not there and it will updated if it's there?

I am still trying to figure out why all the company information for a contact is showing only in the relationship tab instead of the main summary tab.

Thanks again...

hi,

There's currently no way to set the current employer value on import. I'm 99% sure there's an existing Jira issue for this, as it's definitely a loophole in the existing process.

Issue is here CRM-3532
and it's already fixed in CiviCRM v2.2

kiran