04-01-2013 02:07 PM - edited 04-01-2013 02:08 PM
OOTB it looks like SLX prevents deletion of SLX user accounts if the user is a team owner, or if the user has objects where they are the owner.
We have a business need to include another rule - if the user is listed as the Account Manager on any opportunities, and they don't own the account the opp is assigned to (for example, if they are on a team owned account, and the user is listed as account manager for an opp from that account)
The specific problem is we are storing some data in the USER_PROFILE table that is still needed for reporting, where the account manager ID is the main data element used in reporting. In our example, we want to be able to report on data that uses some values stored in USER_PROFILE.
I have observed that upon deletion, the user ID in the accountmanagerid field is not updated, so you have opportunities that look like they have owners, and are accessible by others on the same team as the Account owner, but no other data. I pulled up an Opp that belonged to a deleted user and the account manager lookup control was just blank. In addition, the History table isn't written to if the account manager is changed.
Does anyone have any insight on what kicks off the deletion in SLX LAN and fires back the warning re: object ownership, and how we can tap into it to add this extra criteria? Is it a DB trigger?
04-01-2013 03:09 PM
04-01-2013 03:39 PM
04-01-2013 05:07 PM
04-04-2013 11:52 AM
04-04-2013 12:06 PM
.. foreign keys... if you delete a user you get "broken foreign keys" in your history table and your performane drops instantly.
Never delete a user.. just retire.