- Merge data within the same categories first before working on cross-type dups. For example: Client vs client, Partner vs Partner; Prospect vs Prospect, etc. It helps to narrow down the batch size and is probably safer when starting to merge dups. (save me a lot of headaches)
- Building Data Quality/Merging score: depends on your Salesforce and fields. It would help when merging cross-type dups (i.e Client vs Prospect).
- If you use the mass merge tool, make sure to analyze the data and data type first. Then adjust the merging rule behavior for each field if possible. For example, the tool I'm using allows me to concatenate the long text field if this field is populated in all dups. Or get the sum amount or max number depending on the fields.
I'm sure that many Salesforce admin already encountered the this Process builder error when building automation referencing a field on a related record (aka lookup field): ' The flow failed to access the value because it hasn't been set or assigned ' and came across this Salesforce document . However, it does not help in case of referencing a User lookup field. ------------------------------- Use case: when a lead's ownership is transferred to another user, respective fields are updated based on their profile. Error element myDecision (FlowDecision). The flow failed to access the value for myVariable_current.Owner:User.ProfileId because it hasn't been set or assigned. --------------------------- Workaround: Have a condition to check if the record is assigned to a user or a queue before checking their profile id for respective actions. Records owned by user: BEGINS([Lead].OwnerId, "005") Records owned by queue: BEGINS([Lead].Owne...
Comments
Post a Comment