Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In an org with Duplicate Management set to 'allow', dlrs cannot update a duplicate Lead or Account. An exception is thrown. #1007

Open
colinkenworthy opened this issue Dec 11, 2020 · 0 comments

Comments

@colinkenworthy
Copy link

colinkenworthy commented Dec 11, 2020

Is your feature request related to a problem? Please describe.
The rollup field is not updated and Apex exception emails go out

Describe the solution you'd like
DML Options can be used on the update to allow the update to succeed.
[DMLOptions.DuplicateRuleHeader Class](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_class_Database_DMLOptions_DuplicateRuleHeader.htm#apex_class_Database_DMLOptions_DuplicateRuleHeader
or the SObject.setOptions(DMLOptions) method.
It would be good for the update to happen and the rollups on duplicate records to be correct. I can't think of any reason not to use this DML Option, unless it affects sObjects not under duplicate management.

Describe alternatives you've considered
none

Additional context
Perhaps it is possible to make the DML Options part of the rollup setup screen so users can decide if they want the exception or an update to happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant