* Sales Cloud - Best Practices *

@Gurjot Kaur

- when you're referencing a flag in flow, are you thinking custom notification? It would pop in the user's desktop notification tray or via push notification if they closed it via mobile but maybe?  

We also use the rich text component with conditional visibility. I wonder if there's a way to add another piece of conditional visibility criteria that says ClosedDate = Today? So, it would show for everyone on that day but would not show again after? Not the most elegent but /shrug

Hi @Renu Mudhalwadkar

,  

did you ever find out the reason for the described behavior?  

I noticed the same behavior. When we search for a user in "Owner" filter we only see "XXX 's Team" as result coming up, even though this user doesn't have a role below him/her in role hierarchy (and doesn't have a team) and I don't know why. 

I still shows the correct data, but it is irritating for the users/managers. 

Thanks, Sue

First thing to verify is Contact OWD: 

 Go to Setup --> Sharing Settings --> Organization-Wide Defaults and check the Contact setting.

• Public Read/Write --> users should generally retain access to Contacts. 
• Public Read Only --> users should still be able to view the Contact. 
• Private --> access depends on ownership, role hierarchy, sharing rules, teams, etc. 
• Controlled by Parent --> Contact access is determined by access to the related Account

Additionally, other things to verify:

• Check Contact Sharing Rules, especially owner-based rules
• Check Account Sharing Rules if Contacts are Controlled by Parent 
• Check Role Hierarchy of the old and new Contact Owner 
• Check Manual Sharing

 The toast itself is essentially the symptom: Salesforce changed/recalculated access, determined that the current user no longer has access, and closed the record tab. 

You’re very close — the key is that Salesforce distinguishes between task assignment emails and task reminders.

If you’re using Lightning Experience, disabling Enable User Control Over Task Assignment Notifications and enabling the Email Notification Checkbox on the Task page layout won’t give you the behavior you’re expecting. Salesforce documents that the Send Notification Email checkbox is effectively a Salesforce Classic feature; it isn’t displayed on the Lightning New Task experience. Salesforce

If your goal is “Create a task for myself and email me when it becomes due”, standard task assignment notifications aren’t really designed for that. They primarily notify someone when a task is assigned to them, and Salesforce specifically notes that notification emails generally aren’t sent when users assign tasks to themselves under the user-controlled notification model.

Hi @Vishal Verma

--->>>

how will the Trigger know which other policies the message should link to. But it hints to a solution.

Maybe if the conversation is still open with Support, then also ask them if it is possible to control this from the Salesforce Outlook Add-In which you are currently using. Is there a way to specify more policies (or other entities) to upload the email to? 

Could you please Guide me on this ?

Hi Katie,

The duplicate value error you are encountering (csp__Unique_Key__c) happens because that custom field is marked as Unique (likely enforced case-insensitively or case-sensitively) in your schema settings, and both contact records currently hold conflicting or populated values that clash during the merge operation. When Salesforce attempts to merge the records into the winning record, it briefly retains or evaluates the unique keys of both records simultaneously, triggering the block.

Here is how you can resolve and complete the merge: 

1.Clear or Modify the Unique Key on the Losing Record:

Field Modification. 

Navigate to the losing contact record, edit the csp__Unique_Key__c field, and either clear out the value entirely or temporarily change it to a distinct placeholder string. You can verify success when saving the edited record without a duplicate value validation error. 

2.Perform the Contact Merge:

Execute Merge. 

Return to the contact merge tool and execute the merge while selecting the correct master record. You can verify success when the merge completes without throwing the ConMergeException block. 

3.Verify the Winning Record's Unique Key:

Post-Merge Cleanup. 

Check the winning contact record to ensure its csp__Unique_Key__c matches the correct integration ID needed by Classy. You can verify success when the integration key on the surviving record is accurate and uncorrupted.