Author Topic: Drupal user <-> CiviCRM records -- 1:1 or 1:many (Read 1096 times)

bchoc · January 26, 2008, 01:56:33 pm

Really quick question. In 1.6, there was a definite 1:1 between Drupal accounts and CiviCRM records. For example, if a related Individual record was created at signup, and later a Form allowed an associated Organization record to be created, the latter would wipe out the former.

Is this still the case with 1.9 & 2.0?

bc

Dave Greenberg · January 28, 2008, 12:59:03 pm

There should always be a 1:1 relationship between Drupal users and CiviCRM contact records. This constraint is represented in the schema - the civicrm_uf_match table stores the relationship - and the Drupal user id (uf_id in that table) is unique per domain.

I'm not quite sure what work-flow you're referring to in "later a Form allowed an associated Organization record to be created ..." ??

If you are referring to an issue where the contact type was inadvertantly changed during a My Account / Profile update - that should be fixed: http://issues.civicrm.org/jira/browse/CRM-1061

But really, the best bet is for you to test out your specific case in 2.0 - and either repost w/ a question here - or file an issue if the behavior you're seeing seems to be buggy.

bchoc · January 29, 2008, 03:10:08 pm

When I did my first CiviCRM install under 1.6 a year ago, I set things up so that at Drupal signup users filled in a few fields in a linked Individual records. Later, via a profile, these same users were linked to an Organization record. I observed that saving the latter wiped out any information in the former. I inquired on (at that time) the mailing list and was told this was the way it was built, but it might change.

As I plan a 1.9/2.0 build, I just wanted to confirm whether this has evolved or not and design accordingly.

It seems it's the same.

bc

Dave Greenberg · January 29, 2008, 05:26:18 pm

I'm not sure what you mean by "via a profile, linked to an organization record...". As I noted, a user may only be directly associated with a single contact record (which has a "type" of either Individual or Organization). Individuals can be "linked" to one or more organizations within CiviCRM's datastore via Relationships.

There has been some discussion about implementing permissioning on those relationships (i.e. give an individual contact permission to update info for an organization that they have a special relationship with). However, this is still on the medium term road-map and probably won't happen until we get some sponsoring organization(s).

It might be best for you to try out your flow in 2.0 - and see how it's working for you.

bchoc · January 29, 2008, 06:21:03 pm

If you access the Drupal-synced record using a Profile which is comprised of Individual fields. Then you use a Profile which is comprised of Organization fields to access the Drupal synced record.

Under 1.6, the Individual data would be lost and an Organization record would be created.

So, in a nutshell, a Drupal user can have edit rights to either one or the other, but not both. Again, this was under 1.6. Basically, it seems it's still the same.

bc

CiviCRM Community Forums (archive)

News:

Author Topic: Drupal user <-> CiviCRM records -- 1:1 or 1:many (Read 1096 times)

bchoc

Drupal user <-> CiviCRM records -- 1:1 or 1:many

Dave Greenberg

Re: Drupal user <-> CiviCRM records -- 1:1 or 1:many

bchoc

Re: Drupal user <-> CiviCRM records -- 1:1 or 1:many

Dave Greenberg

Re: Drupal user <-> CiviCRM records -- 1:1 or 1:many

bchoc

Re: Drupal user <-> CiviCRM records -- 1:1 or 1:many