merge uses wrong assigned_to_user

[eaho]

I have consistently seen that when an account or contact is "merged", that the "assigned_to_user" field is set to user XX, but user YY (the other option for the merge) is used when the two contacts or two accounts are merged.

When a new contact is made from the merger, that contact uses all the data that it was supposed to except for the "assinged to user" field.

I have been using SugarCRM for nearly a year, but I am running the latest version (updated last week).

Is there a fix for this problem?


thank you,
eaho

[roblaus]

Hi,

Yeah, I know what you mean. The only way is to move the owner field manually (with the arrows) to the right position. I guess this is intended because if a duplicate entry has two owners - which one is the correct one? The one whose entry is more correct? Or the one you choose arbitrarily? Or asked differently: If a record is owned by salesrep A and a (better) duplicate is created by secretary B - which owner would you like to keep?

rgds
rl

[eaho]

The merge feature allows you to specify which user (userA or userB) you want to be the record owner. However, when the merge request is processed, the specified assigned user is not used in the new contact.

If I merge two contacts or two accounts, I have textboxes containing data for the new contact. All those fields (like firstname, lastname, etc) seem to work except for assigned user. I specify UserA in that textbox, but the new contact (or account) created by merging ends up being userB.

The arrows work. But the information held in the textbox is not used by the merged contact/account.

With multiple users that search "their" contacts and accounts, not being able to specify the correct user means SugarCRM is creating bad data in my database.

[roblaus]

Are you using Pro? I checked it now for leads and contacts in OO and the chosen user was kept. Might be different in the Pro version.

[eaho]

I was using Pro. Switched to OO.

I made an OO installation, changed it up a bit to match as best it could to the Pro. Just pointed the OO code at the Pro database and everything seems to be working. The last version of SugarCRM really helped by eliminating long-standing bugs that caused parts of the system to not work for us. Unfortunately, I can't specify if this particular bug is new or old.

I am using OO Version 4.5.1c (Build 1269).

[roblaus]

Sorry, I always mess up OO and OS, probably because I use both.

However, I documented what I did - pls. comment.

rgds
rl

[eaho]

Thank you for looking into it and great job on documenting.

If I do the steps you provided, I get the same results. However, if I had left Robert as Robert (and not made it Kati), it would have still assigned Kati to be the assigned to user. This is true even if I select another user (from using the select button). The arrows work fine, the textboxes work fine, but the merge 'assigned by' seems to only use the user on the right, and not the one in the textbox.

Ethan

[roblaus]

I'll have a look at it a little later but you may be right, I never saw it from this angle.

rgds
rl

[roblaus]

Yes, you are right, I guess this is a bug - it always takes the user on the "right" side (the non primary one). Took me some time to realize what you meant. I will file a bug if it is not there already.

rgds
rl

[eaho]

Thank you. I'm not familiar with how the bug reporting works for SugarCRM. Can you post the bug report link in this forum by chance? I'd like to monitor it. While it's sad that it's a bug, at least it's consistent (which hopefully means it's easier to debug). Glad to know I wasn't "seeing things".

Ethan