(default organization) contact issue and questions

[aglozier]

I just noticed that there is a duplicate contact for our organization in the database.  It is called "Phoenix Academy (default organization)".  I assume this is a new feature of 4.3 and that the contact was added during the database update using the "Organization Address and Contact Info".

This system detects that this is a duplicate contact and tries to merge it into the original contact, but the "default organization" contact isn't deleted.  Also I can't manually delete it and I get a message saying "This contact is a special one for the contact information associated with the CiviCRM installation for this domain. No one is allowed to delete it because the information is used for special system purposes."  I flipped the merge order and was able to merge the original into the "default organization" contact.

My question and concern is: why did the database update add a new contact instead of making the original one the default?  One thing that might have a bearing on this is that I didn't have a email address entered in the "Organization Address and Contact Info".  Also is there a way to manually set the "default organization"?

[Dave Greenberg]

Thanks for report on this. Starting w/ 4.3, a default domain contact record is required (and hence the upgrade creates one using the info previously entered in the 'Organization Address and Contact Info' screen.

I've investigated a bit - but awaiting feedback from the team as to whether the upgrade was "supposed" to identify the existing 'matching' organization contact. I suspect not - so the merge you did was the appropriate step. That said, I think an upgrade status message is needed to inform folks that a new organization contact was created. I'll report back here.

You can not manually set the "default organization" currently (not in the UI at least), so again the merge you did was the way to go in terms of 'moving' any key info and relationships TO the default organization.

[CallFirst]

Add additional organizations to the "default organization" currently (not in the UI at least), so again the merge you did was the way to go in terms of 'moving' any key info and relationships TO the default organization.

The ability to differentiate organizations in memberships is a sweet feature.

Where is the code "select" statement running that would pull the organization choices?

thanks in advance.

[aglozier]

Once I used the same email address for my organization contact and for the "Organization Contact Information", the upgrade correctly made my organization the default and didn't create a duplicate

[Dave Greenberg]

Add additional organizations to the "default organization" currently (not in the UI at least), so again the merge you did was the way to go in terms of 'moving' any key info and relationships TO the default organization.

The ability to differentiate organizations in memberships is a sweet feature.

Where is the code "select" statement running that would pull the organization choices?

thanks in advance.

Any Organization contact in your DB is eligible to be the 'owner' of a Membership Type (label is Membership Organization in the Add Membership Type form and it's an autocomplete field selecting all org contacts).

[rares]

Just to add my two cents here. We are running 4.4.1 we discovered that when merging contacts, when one is the default organization, you can merge the other contact into the default organization, but not the other way around.
This makes sense, but in our case we didn't even know there was such a thing as a default organization, and CiviCRM definitely gave no feedback saying that the merge failed. On the contrary, it said that the merge succeeded:

"Contact id 18648 has been updated and contact id 20446 has been deleted." (but neither contact was deleted)

We were able to complete the merge by flipping between the contacts on the merge screen.

Dave, is this worth reporting as a bug?

[Donald Lobo]

hey rares:

yes, can you please file an issue for this. We should definitely prevent errors which cause issues down the line

thanx

lobo

[JoeMurray]

Thanks, rares, for reporting this. One of my clients is experiencing the same issue after an upgrade. Could you post back here a link to the issue?

Cheers,
Joe

[Detlev]

Something similar happened to me and is described here:
http://forum.civicrm.org/index.php/topic,30595.msg131089.html#msg131089

However, in our case the default organisation *was* put into the trashbin during merging, however was not able to be deleted completely nor to be undeleted.

[Dave Greenberg]

I've posted an issue for this at http://issues.civicrm.org/jira/browse/CRM-13780