SLX 8 Web Merge accounts issue

[apfingstl]

We have added hopefully all secured actions to the standard user group which are required to merge records.

Scenario 1:

A user tries to merge two accounts owned by a team.

This works fine.

Scenario 2:

A user tries to merge two accounts owend by "everyone".

The user gets an error saying "you do not have security permissions for this records."

This happened in 8.0 eval db.

Has someone seen and maybe solved this?

Thanks! Alexander

[MikeSpragg]

Only Admin can merge Everyone records. If you are using teams – you should re-align Everyone to a team, rather than Everyone. Or, if really Everyone then, again, only Admin user can Merge/change owner for these recs owned by Admin. There is no workaround to that. Otherwise anyone can change ownership - including making an Everyone account private.

[apfingstl]

Hi Mike,

I do not understand this.

If you merge two accounts which have the seccodeID of everyone, the resulting account will be everyone.

So why does SLX give an error here?

Thanks! Alexander

[MikeSpragg]

It's not relevant what the resulting owner would be - only that the user cannot touch (inc. merge) an owner of everyone.

[RJLedger]

Agree with @MikeS.

Ever since 4.02 I've used a "Best Practice" of creating a special team that has every SalesLogix user in it. We use it in place of "EveryOne"

[apfingstl]

Hi All,

I disaggree a little.

I understand that everyone can not be changed by a user, only by admin.

I am asking myself if this is best for the cufrrent time and situation we are now in.

But what I do not understand is, if you merge two everyone accounts, I would expect that this works.

I can understand that it fails if one account is not everyone, but if both are, I would expect it to work.

Alexander

[MikeSpragg]

OK. Cut to the chase - you can't do it. Move on!

[apfingstl]

A Customer called today and set that in 7.5.4 web a user could merge two accounts where the owner of both is everyone.

Thanks! Alexander

[apfingstl]

Web Core Update 03 seems to fix this issue. At least it is part of the defects in the list fixed in this issue. Have not tested it.