Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.At the moment only the account name is synced to the user and it's put into the given name field.
As far as I can tell no other issue is tracking this behavior since #2704987: [META] Finish incomplete match field handlers and related are concerned with matching of contacts between each other. Have there already been plans on how to define that mapping of simple fields between users and contacts?
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | primary-email-mapping-sync-3043141-10.patch | 9.4 KB | grahl |
| #5 | interdiff-3043141-2-5.patch | 8.31 KB | grahl |
Comments
Comment #2
grahlAttached is a very rudimentary patch to add the primary email field to the synchronization.
I'd be happy to work on a more general patch if I'd know that I'm on the right track in terms of the overall approach.
Comment #3
RoSk0Hi @grahl,
In general I would prefer to avoid data duplication or at least make it configurable so users can decide copy or not, but in general you are on a right track.
About the meta issue you mentioned: its probably poor naming that confusing but there is a huge difference between "CRM Core User Synchronization" module which is a means of relate user to a contact and "CRM Core Match" module from the meta above which provide means to find duplicating contact records based on different matchers.
Comment #4
grahlComment #5
grahlWhile not perfect yet the updated patch adds the common functionality of checking for a matching email first, when enabled, and makes syncing usable.
Comment #6
grahlComment #8
grahlAdds a missing schema declaration
Comment #10
grahlComment #11
grahlComment #12
grahlComment #14
RoSk0Thanks Hendrik.